./recovery.sh -p <password> -s <failing_engines> -ni
Jesus
Discussion posts and replies are publicly visible
Thanks for your answers. We use a script that copies the folders from the backup and have been used in multiple upgrades without problems. The cp command did not return any failure.
We also stop Appian in the order indicated in the documentation: tomcat, search-server,. data-server, services
Hi all again,
I am attaching the service manager log with the transaction exception that was added for one of the engines. Other failing engines show a similar error. Is it possible to recover the engines knowing the transaction id without losing running processes? Or at least minimising the number of instances lost?
2024-11-25 13:47:50,920 [KafkaTransactionLogService [execution00]-execution00-REPLICA STARTING] INFO com.appian.komodo.log.KafkaTransactionLogService - execution00 REPLICA transaction log state calculated in 2 seconds: TransactionLogState{appendedCount=14879, firstTransactionId=Optional[8050800], lastTransactionId=Optional[8065678]} 2024-11-25 13:47:50,921 [shared-cached-threadpool-10] ERROR com.appian.komodo.translog.TransactionReplayer - Unable to find transaction 1 in the transaction log for execution00. Please verify that an old kdb was not used. 2024-11-25 13:47:50,921 [shared-cached-threadpool-10] ERROR com.appian.komodo.translog.TransactionReplayer - Transaction replay failed for execution00 com.appian.komodo.translog.TransactionNotFoundException: null
It seems that checkpointing did not occur properly when stopping the Appian services, which caused the error. To avoid this, ensure that engines are checkpointed properly after stopping the Appian services. Alternatively, you can run a manual checkpoint before stopping the Appian engines.