We ran into an issue with our Appian instance and figured out that it stopped wo

RE: We ran into an issue with our Appian instance and figured out that it stopped wo

asifh — Sun, 31 Mar 2019 11:53:12 GMT

Nicholas Wurster.. kindly let us know how did you resolve this issue. We are facing the similar issue right now.

RE: We ran into an issue with our Appian instance and figured out that it stopped wo

Nicholas Wurster — Wed, 09 Dec 2015 00:38:38 GMT

Thanks for providing the feedback, we have got past our issues and working forward again and chalking this up to a big lessons learned. Will be making some changes to our development management strategy to reduce the impact should it happen again.

RE: We ran into an issue with our Appian instance and figured out that it stopped wo

christopherl — Tue, 08 Dec 2015 20:26:25 GMT

Sorry. To clarify, I did not mean to imply you should do this without the input and guidance of support.

RE: We ran into an issue with our Appian instance and figured out that it stopped wo

Eliot Gerson — Tue, 08 Dec 2015 20:11:40 GMT

Important: Please do not rollback kdb files without consulting Appian Support. Improper rollbacks can cause unpredictable and problematic behavior in the environment and you should never roll back or otherwise alter your kdb files unless specifically instructed to do so by Appian Support. As Christine mentioned, the best course of action in such a situation is to contact Appian Support--the sooner, the better.

We encourage customers to take advantage of the Documentation and other resources on Forum to solve problems and answer questions--and we certainly appreciate your effort to do so in this case. At the same time, please do not hesitate to contact us for further assistance if needed; that's what we're here for!

RE: We ran into an issue with our Appian instance and figured out that it stopped wo

christopherl — Tue, 08 Dec 2015 06:39:38 GMT

Depending on how you cleaned up, you may have ended up with KDBs out of sync since they could not write to disk. Generally, after a full filesystem, it is best to roll back the KDB files to a known-good working state where you have an entire set with the same timestamp.

As a best practice, your developers should be exporting packages of their daily work just to safeguard against environment problems that could cause a loss of data. If they have done so, and you still have a full set of time-matched KDB files from before the out of space problem occurred, I would roll back the KDBs and re-import your applications.

This scenario is why scheduled cleanups are so important. One other thing to keep an eye out for is orphaned active processes resulting from development activity. If your process models don't have a parallel expiration flow you can end up with a few thousand active processes just sitting in memory inflating the size of your KDB files which exacerbates storage problems.

I too would recommend opening a support ticket as you could have underlying object ID mismatches lurking in your KDB files that could cause you problems down the road and will be very difficult to isolate the cause of.

RE: We ran into an issue with our Appian instance and figured out that it stopped wo

ChristineLHutchison — Tue, 08 Dec 2015 05:27:36 GMT

I would open a support case. They are always very helpful with the proper steps of recovery after an improper shutdown.