Rolling back transactions

The rollback-transaction task rolls back an active (uncommitted) transaction for a specified Record Store instance. Once a transaction is rolled back, this can not be undone.

The syntax for this task is:
recordstore-cmd rollback-transaction  -a RecordStoreInstanceName -x Id
[-h HostName] [-l true|false] [-p PortNumber]
where:
  • -a (or --instanceName) specifies the name of a Record Store instance. Required.
  • -h (or --host) specifies the host where the Endeca CAS Service is running. If the flag is omitted, the default is the value of the com.endeca.itl.cas.server.host property in commandline.properties. If the property is not set, the value then defaults to localhost. Optional.
  • -l (or --isPortSsl) specifies whether to communicate with the service using an HTTPS connection. A value of true uses HTTPS and treats the com.endeca.itl.cas.server.port property as an SSL port. A value of false uses HTTP and treats com.endeca.itl.cas.server.port as a non-SSL port. Specify false if you enabled redirects from a non-SSL port to an SSL port. Optional.
  • -p (or --port) specifies the port of the Endeca CAS Service. If the flag is omitted, the default is the value of the com.endeca.itl.cas.server.port property in commandline.properties. If the property is not set, the value then defaults to 8500. Optional.
  • -x (or --transaction) specifies the ID of the transaction that is rolled back. Required.

Note that uncommitted transactions are often the result of an unexpected termination of a crawl. In this case, you see an error in the log file that includes the ID of the uncommitted transaction.

Example of a transaction rollback

This example rolls back the transaction with an ID of 7:
recordstore-cmd rollback-transaction -a RS1 -x 7
If the command succeeds, it prints the following message:
Rolled back transaction: 7
If the command fails, it prints the following error message:
Failed to roll back transaction: 7