accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3027) Introduce configuration Property's for Master wait times
Date Tue, 29 Jul 2014 15:07:38 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Newton updated ACCUMULO-3027:
----------------------------------

    Fix Version/s:     (was: 1.5.2)
                       (was: 1.6.1)

Agreed that it is potentially a low-risk improvement.  The number of watches introduced would
be trivial because only the master really needs to watch them.  But, consider the possibility
that the best way to implement this is to create a new class, which acts as a proxy to the
ZooCache.  The same proxy would be advisable for several other settings which presently require
a restart for updates to take effect.  Now you have a more substantial refactoring that should
not be back-ported.  All that said, I'm not strongly opposed to back-porting, I'm just advising
against it.  I'm removing the branch fix versions, but if you put them back, I won't object.

> Introduce configuration Property's for Master wait times
> --------------------------------------------------------
>
>                 Key: ACCUMULO-3027
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3027
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Josh Elser
>            Priority: Minor
>             Fix For: 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):
> * TIME_TO_WAIT_BETWEEN_SCANS
> * TIME_BETWEEN_MIGRATION_CLEANUPS
> * WAIT_BETWEEN_ERRORS
> * DEFAULT_WAIT_FOR_WATCHER
> * MAX_CLEANUP_WAIT_TIME
> * TIME_TO_WAIT_BETWEEN_LOCK_CHECKS
> * MAX_TSERVER_WORK_CHUNK
> * MAX_BAD_STATUS_COUNT



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message