accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ShawnWalker <>
Subject [GitHub] accumulo issue #121: ACCUMULO-4353: Stabilize tablet assignment during trans...
Date Thu, 07 Jul 2016 14:11:17 GMT
Github user ShawnWalker commented on the issue:
    > 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.
    Indeed, I found this out when I went to implement my idea.  So in my most recent push,
I modified the the thrift method `TabletClientService.unloadTablet(...)`.  Whereas it used
to take a `boolean save` parameter, I instead have it take an enumerated value describing
the desired end state of the tablet:
    * UNASSIGNED: Upon unloading, leave the tablet in the UNASSIGNED state.
    * SUSPENDED: Upon unloading, leave the tablet in the SUSPENDED state.
    * DELETED: Upon unloading, leave the tablet in the UNASSIGNED state.  This tablet is being
unloaded so it can be deleted soon; as such, don't bother minor compacting before unloading.
 This is the behavior that setting `save==false` would accomplish previously.
    * UNKNOWN: Well, ugh.  The enumerated value needed to correspond with values from `master.Master.TabletGoalState`,
and I had no idea how to cleanly map `TabletGoalState.HOSTED`.

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