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] [Commented] (ACCUMULO-3027) Introduce configuration Property's for Master wait times
Date Tue, 29 Jul 2014 13:53:39 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077721#comment-14077721
] 

Eric Newton commented on ACCUMULO-3027:
---------------------------------------

I don't support backporting this improvement to 1.5 or 1.6 until it fixes a known problem
in those branches.  We should be very conservative with our changes to released versions.
 I think this would be a straightforward change, but if it doesn't fix anything I would prefer
to see it only in a new release.

> 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.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):
> * 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