[
https://issues.apache.org/jira/browse/HBASE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524450#comment-16524450
]
Andrew Purtell commented on HBASE-20745:
----------------------------------------
Intentional?
{noformat}
diff --git
a/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
b/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
index 3412c82f2d..d1e6e85f3c 100644
---
a/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
+++
b/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
@@ -136,7 +136,7 @@ public class AssignmentManager implements ServerListener {
public static final String RIT_CHORE_INTERVAL_MSEC_CONF_KEY =
"hbase.assignment.rit.chore.interval.msec";
- private static final int DEFAULT_RIT_CHORE_INTERVAL_MSEC = 5 * 1000;
+ private static final int DEFAULT_RIT_CHORE_INTERVAL_MSEC = 60 * 1000;
public static final String ASSIGN_MAX_ATTEMPTS =
"hbase.assignment.maximum.attempts";
{noformat}
Can we revert this bit and put it in with a separate JIRA? Or was this part of
a fix for something already logged?
> Log when master proc wal rolls
> ------------------------------
>
> Key: HBASE-20745
> URL: https://issues.apache.org/jira/browse/HBASE-20745
> Project: HBase
> Issue Type: Sub-task
> Components: debugging
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.0.2
>
> Attachments: HBASE-20745.master.001.patch
>
>
> Emit when we roll master proc WAL so can see when they happen. Want to
> correlate instances of corruption w/ events on Master. Currently hard to do
> on a server where log-level is INFO (default for many deploys).
> Also, we log STUCK regions every 5 seconds. If a bundle of regions get stuck,
> we can log so frequently, we roll away where the problem happened so lose the
> chance to debug. Let me fix that too....
> Need both debugging instances of parent issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
