MongoDB update failure Solution

Symptom:

Writeresult res = your template. updatefirst (query, updateobj, "servertoagentreq_sms ");

When obtaining the res. getn () return value, it is found that the return value is 0 occasionally, indicating that the update operation has not updated any data. In addition, the probability of failure is greatly increased if multiple threads are concurrently updated.

The official website says the update operation is not guaranteed to be successful ....

Solution:

After one failure, another thread tries multiple times.

 

  Private Threadpoolexecutor exec = New Threadpoolexecutor (2, 10, 3, timeunit. Seconds, New Arrayblockingqueue <runnable> (10 ), New  Threadpoolexecutor. callerrunspolicy (); mainCode: Writeresult res = Jsontemplate. updatefirst (query, updateobj, "servertoagentreq_sms");  //  If the update fails, enter another thread to retry the update.              If (Res. getn () = 0 ) {Exec.exe cute (  New  Runnable () {@ override  Public   Void  Run (){  Int Num = 0 ; Writeresult res = Jsontemplate. updatefirst (query, updateobj, "servertoagentreq_sms");  While (Res. getn () = 0 & num <100 ) {Res = Jsontemplate. updatefirst (query, updateobj, "servertoagentreq_sms" ); Num ++ ;  Try  {Thread. Sleep ( 300 );}  Catch  (Interruptedexception e) {logger. Error ( "Failed to respond to update {}", E );}}  If (Res. getn () = 0 ) {Logger. Error ( "An error occurred while responding to the update !!! Gwmsgid :{}, masmsgid :{}" , Gwmsgid, masmsgid );}}}); 

The failure rate is greatly reduced.