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/08/05 14:08:48 UTC

[GitHub] [accumulo] ctubbsii commented on pull request #2846: Added logging to try and find the cause of the intermittent ZK failures

ctubbsii commented on PR #2846:
URL: https://github.com/apache/accumulo/pull/2846#issuecomment-1206499320

   The advantages of using a separate process for initialization are:
   1. It reflects how users initialize, and exercises that process,
   2. It avoids tainting any JVM-wide static state from the initialization process in the IT client code, and
   3. It avoids treating the IT code as inherently part of the server side of things. Most ITs behave as Accumulo clients, not server-side utilities, and shouldn't be running server code in-process.
   
   I don't see why running initialize in-process would help. It should suffice to wait for the initialize process to complete successfully, and then, if necessary, synchronize the IT with ZK.


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