Inconcistency between backends of the same controller may take down the 2 
backends at once
------------------------------------------------------------------------------------------

         Key: SEQUOIA-951
         URL: https://forge.continuent.org/jira/browse/SEQUOIA-951
     Project: Sequoia
        Type: Bug
    Versions: Sequoia 2.10.7    
    Reporter: Stephane Giron
 Assigned to: Stephane Giron 
    Priority: Critical
     Fix For: Sequoia 2.10.8


It seems that the way a task is updated by BackendWorkerThreads can lead to 
several backends going disabled, as shown on the following log:

2007-05-16 15:20:50,882 ERROR backend.DatabaseBackend.c1b1 Disabling backend 
c1b1 that reports a different number of updated rows (4) than first backend to 
succeed (3) for request update test set i = i+1/
2007-05-16 15:21:04,872 ERROR backend.DatabaseBackend.c1b2 Disabling backend 
c1b2 that reports a different number of updated rows (4) than first backend to 
succeed (3) for request update test set i = i+1/ 

It seems that it is also possible that the result that is sent back to other 
controller can be wrong : the result that is sent can be the one that was got 
on the disabled backend.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to