accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From keith-turner <>
Subject [GitHub] accumulo issue #121: ACCUMULO-4353: Stabilize tablet assignment during trans...
Date Thu, 07 Jul 2016 13:47:28 GMT
Github user keith-turner commented on the issue:
    > My current thought would be to make unloading a tablet this way suspend the tablet
instead of unassigning
    I took a quick look and it seemed a tserver did not know why it was unloading.   It seems
like the tserver would need to know why it was unloading so it could only suspend when being
stopped (would not want to set suspend for migration).  Alternatively the unload thrift message
could possibly be changed to include an option to suspension.
    Would need to analyze the master and tserver code for concurrency issues if taking this
approach.  Currently only the master is writing suspend.
    >  Hence, running a tserver with tserv.port.client==0 will render Admin.stopTabletServer(...)
ineffective, and will fall back to sending SIGTERM/SIGKILL to stop the tserver.
Similarly, running a tserver with risks the same behavior.
    That's an interesting find.  Can you open a new issue for this?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message