accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1454) Need good way to perform a rolling restart of all tablet servers
Date Tue, 12 Aug 2014 03:05:12 GMT


Sean Busbey commented on ACCUMULO-1454:

[~mdrob], presumably the sidecar could be started with its own ACCUMULO_CONF_DIR with the
port set to a different value. 

Relying exclusively on dynamic ports would preclude rolling restarts for anyone running in
an environment that requires whitelisted network comms (e.g. those running under DISA STIGs).
But we could just call out needing to pick a port in whatever docs are describing how to set
up a custom conf dir and make '0' the common case.

> Need good way to perform a rolling restart of all tablet servers
> ----------------------------------------------------------------
>                 Key: ACCUMULO-1454
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.4.3, 1.5.0
>            Reporter: Mike Drob
> When needing to change a tserver parameter (e.g. java heap space) across the entire cluster,
there is not a graceful way to perform a rolling restart.
> The naive approach of just killing tservers one at a time causes a lot of churn on the
cluster as tablets move around and zookeeper tries to maintain current state.
> Potential solutions might be via a fancy fate operation, with coordination by the master.
Ideally, the master would know which servers are 'safe' to restart and could minimize overall
impact during the operation.

This message was sent by Atlassian JIRA

View raw message