accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3027) Introduce configuration Property's for Master wait times
Date Tue, 29 Jul 2014 14:43:38 GMT


Josh Elser commented on ACCUMULO-3027:

Yes, the test for ACCUMULO-2694 is the primary reason I created this. I can also see value
in being able to control some of these values on a system (debug a problem, faster recovery
from unexpected circumstances, etc) without having to perform a code change.

While I don't think making configuration parameters for otherwise hard-coded values is a very
risky operation (sans maybe an impact on extra ZK watchers), I'm not really set on where (all)
this gets done. If it still gives you pause, feel free to nuke the older fixVersions.

> Introduce configuration Property's for Master wait times
> --------------------------------------------------------
>                 Key: ACCUMULO-3027
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Josh Elser
>            Priority: Minor
>             Fix For: 1.5.2, 1.6.1, 1.7.0
> From the comment in the patch for ACCUMULO-2694, the Master has a few wait values that
are hardcoded. We should introduce new entries in Property and set the current values as the
default. Also has the added gain of providing meaningful descriptions of how the parameters
is used by the Master (or TabletGroupWatcher):

This message was sent by Atlassian JIRA

View raw message