You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2022/09/09 14:49:23 UTC

[GitHub] [accumulo-testing] keith-turner commented on issue #219: Security.xml throws exception with randomwalk

keith-turner commented on issue #219:
URL: https://github.com/apache/accumulo-testing/issues/219#issuecomment-1242071790

   I have not looked at this in a long time, so not completely sure the following explanation is completely correct.
   
   I think the security RW test are broken because the assume that the security APIs are immediately consistent when they are actually eventually consistent.  The security RW test may work better if run w/ a single tablet server but not sure.
   
   I think when an Accumulo client does a security operation it picks a random tablet server to actually carry out that work.  The tablet servers store the security information in Zookeeper and use ZooCache to keep a copy of it.  So when one tserver does a security operation it will eventually cause the zoocaches of other tablet servers to update.  That could lead to the following
   
    1. Client A randomly contacts tserver 1 to update some security information
    2. Client A randomly contacts tserver 2 to read the security information it just updated.  Because ZK has not propagated the update yet to tserver 2, Client does not see the update.
   
   Again not sure if my recollection matches the current code.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org