[jira] [Commented] (HBASE-3597) ageOfLastAppliedOp should update after cluster replication failures
[ https://issues.apache.org/jira/browse/HBASE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030217#comment-13030217 ] Hudson commented on HBASE-3597: --- Integrated in HBase-TRUNK #1909 (See [https://builds.apache.org/hudson/job/HBase-TRUNK/1909/]) > ageOfLastAppliedOp should update after cluster replication failures > --- > > Key: HBASE-3597 > URL: https://issues.apache.org/jira/browse/HBASE-3597 > Project: HBase > Issue Type: Bug > Components: replication >Affects Versions: 0.90.1 >Reporter: Otis Gospodnetic >Assignee: Jean-Daniel Cryans > Fix For: 0.90.3 > > Attachments: HBASE-3597.patch > > > The value of ageOfLastAppliedOp in JMX doesn't update after replication > starts failing, and it should. See: http://search-hadoop.com/m/jFPgF1HfnLc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3597) ageOfLastAppliedOp should update after cluster replication failures
[ https://issues.apache.org/jira/browse/HBASE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028585#comment-13028585 ] stack commented on HBASE-3597: -- +1 > ageOfLastAppliedOp should update after cluster replication failures > --- > > Key: HBASE-3597 > URL: https://issues.apache.org/jira/browse/HBASE-3597 > Project: HBase > Issue Type: Bug > Components: replication >Affects Versions: 0.90.1 >Reporter: Otis Gospodnetic >Assignee: Jean-Daniel Cryans > Fix For: 0.90.3 > > Attachments: HBASE-3597.patch > > > The value of ageOfLastAppliedOp in JMX doesn't update after replication > starts failing, and it should. See: http://search-hadoop.com/m/jFPgF1HfnLc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3597) ageOfLastAppliedOp should update after cluster replication failures
[ https://issues.apache.org/jira/browse/HBASE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028452#comment-13028452 ] Jean-Daniel Cryans commented on HBASE-3597: --- That would be called on average once or twice per second on a normal cluster, I'm pretty sure DefaultEnvironmentEdge is a few order of magnitudes more expensive than what those metrics are doing. > ageOfLastAppliedOp should update after cluster replication failures > --- > > Key: HBASE-3597 > URL: https://issues.apache.org/jira/browse/HBASE-3597 > Project: HBase > Issue Type: Bug > Components: replication >Affects Versions: 0.90.1 >Reporter: Otis Gospodnetic >Assignee: Jean-Daniel Cryans > Fix For: 0.90.3 > > Attachments: HBASE-3597.patch > > > The value of ageOfLastAppliedOp in JMX doesn't update after replication > starts failing, and it should. See: http://search-hadoop.com/m/jFPgF1HfnLc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3597) ageOfLastAppliedOp should update after cluster replication failures
[ https://issues.apache.org/jira/browse/HBASE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028445#comment-13028445 ] stack commented on HBASE-3597: -- Looks fine. Aren't all those System.currentTimeMillis() expensive? > ageOfLastAppliedOp should update after cluster replication failures > --- > > Key: HBASE-3597 > URL: https://issues.apache.org/jira/browse/HBASE-3597 > Project: HBase > Issue Type: Bug > Components: replication >Affects Versions: 0.90.1 >Reporter: Otis Gospodnetic >Assignee: Jean-Daniel Cryans > Fix For: 0.90.3 > > Attachments: HBASE-3597.patch > > > The value of ageOfLastAppliedOp in JMX doesn't update after replication > starts failing, and it should. See: http://search-hadoop.com/m/jFPgF1HfnLc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HBASE-3597) ageOfLastAppliedOp should update after cluster replication failures
[ https://issues.apache.org/jira/browse/HBASE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002276#comment-13002276 ] Jean-Daniel Cryans commented on HBASE-3597: --- We're not big users of that field, but AFAIK "replication" is the right one as it's the name of the package. > ageOfLastAppliedOp should update after cluster replication failures > --- > > Key: HBASE-3597 > URL: https://issues.apache.org/jira/browse/HBASE-3597 > Project: HBase > Issue Type: Bug > Components: replication >Affects Versions: 0.90.1 >Reporter: Otis Gospodnetic > Fix For: 0.90.2 > > > The value of ageOfLastAppliedOp in JMX doesn't update after replication > starts failing, and it should. See: http://search-hadoop.com/m/jFPgF1HfnLc -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HBASE-3597) ageOfLastAppliedOp should update after cluster replication failures
[ https://issues.apache.org/jira/browse/HBASE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002273#comment-13002273 ] Otis Gospodnetic commented on HBASE-3597: - btw. this is filed under "replication" component because there is no "cluster replication" component. Maybe it should be added? > ageOfLastAppliedOp should update after cluster replication failures > --- > > Key: HBASE-3597 > URL: https://issues.apache.org/jira/browse/HBASE-3597 > Project: HBase > Issue Type: Bug > Components: replication >Affects Versions: 0.90.1 >Reporter: Otis Gospodnetic > Fix For: 0.90.2 > > > The value of ageOfLastAppliedOp in JMX doesn't update after replication > starts failing, and it should. See: http://search-hadoop.com/m/jFPgF1HfnLc -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
