EdColeman commented on issue #3004: URL: https://github.com/apache/accumulo/issues/3004#issuecomment-1285501238
It could also be a race condition where the table id is reserved / stored in ZooKeeper but the rest of the table creation is in-flight. Looking to see if reordering the creation steps can be reordered so that the "existence" of the table is advertised after the configuration and other step have been created. For things like the balancer - those should execute on the next run loop - as long as the run where the configuration cannot be read, it skips / aborts so that it does not do anything that may not be the correct action (for example, defaulting to the default balancer when a custom balancer should be used) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
