Articles in this section

Why did a server fail to start with "unexpected transaction origin 6"?

Detail

A server can fail to start due to an issue related to the read-touch feature on  Aerospike server version 7.1.0.2 (and below).


Answer

Server version 7.1.0.2 (and below) that support the new read-touch feature may fail to start with following error:

CRITICAL (rw): (rw_request_hash.c:397) unexpected transaction origin 6

The issue (AER-6755) has been resolved in version 7.1.0.3 (and above)

https://aerospike.com/docs/reference/release_notes/server/7.1.0.3-server-release-notes

 

Solution:

  • Disable read-touch feature by commenting out setting in aerospike.conf,
  • Disable read-touch-feature in aerospiek.conf and upgrade
  • Disable read-touch transaction retries by setting transaction-retry-ms to a high value. This may impact other transaction retries.

Notes

A workaround can also be done by temporarily increasing transaction-retry-ms to a high value. This would disable the retries.

https://aerospike.com/docs/server/reference/configuration?ctx=all&ver=8&q=transaction-re#service__transaction-retry-ms


Applies To Earliest Version

7.1

Applies To Latest Version

7.1
Was this article helpful?
0 out of 0 found this helpful