You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "EdColeman (via GitHub)" <gi...@apache.org> on 2023/03/23 17:41:49 UTC

[GitHub] [accumulo] EdColeman commented on issue #3248: Race condition in set property.

EdColeman commented on issue #3248:
URL: https://github.com/apache/accumulo/issues/3248#issuecomment-1481617664

   Pretty sure.  My first thought was that reading the updated value from ZooKeeper during the test would be enough to ensure that the change had committed and would have been propagated.  However, the test would still fail occasionally with the changed value not showing up in the exported table config file.  
   
   Looking at that code - it was reading values from the secondary cache in ServerConfigurationFactory.  Originally, that secondary cache was only being cleared on delete events - mainly to limit memory usage.  Change events were delegated to the prop store.   By clearing the secondary cache on any ZooKeeper change event for a cache Id, it forces the values to be re-read on access. 
   
   This should not impact performance because properties are relatively stable.
   
   With the changes in #3245 I have not been able to get ShellServerIT to fail.


-- 
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