Cassandra Delivery Failure Results In Autorepair
(Doc ID 2779239.1)
Last updated on MAY 26, 2021
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
Why does a Cassandra delivery failure result in an autorepair?
The following errors are observed where the LMTP server fails to deliver large messages:
It appears that the cause of the initial failure is either a config issue on the Cassandra side or network ACLs. This is being investigated and that is not the point of this issue.
The same error can be observed with the "deliver" command, when trying to deliver a large message.
The messages are 90 meg and over 100 meg in size, but they are not unusual for this service. Testing is needed to reach the normal limit of 150 meg.
Again, the fact that the delivery is failing is not the point of this issue.
How is autorepair going to help after a "Server temporarily busy" error?
Nothing was written into Cassandra, so what is there to repair?
This seems like it would make a bad situation worse by increasing the load.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document