You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "terry zhang (JIRA)" <ji...@apache.org> on 2012/08/21 08:00:38 UTC

[jira] [Created] (HBASE-6624) [Replication]currentNbOperations should set to 0 after update the shippedOpsRate

terry zhang created HBASE-6624:
----------------------------------

             Summary: [Replication]currentNbOperations should set to 0 after update the shippedOpsRate
                 Key: HBASE-6624
                 URL: https://issues.apache.org/jira/browse/HBASE-6624
             Project: HBase
          Issue Type: Bug
          Components: replication
    Affects Versions: 0.94.0
            Reporter: terry zhang
            Assignee: terry zhang


now currentNbOperations will not reset to 0 and increase after replication start. Now this value is used for calculate shippedOpsRate. if it is not reset to 0 shippedOpsRate is not correct

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-6624) [Replication]currentNbOperations should set to 0 after update the shippedOpsRate

Posted by "terry zhang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

terry zhang updated HBASE-6624:
-------------------------------

    Attachment: jira-6624.patch
    
> [Replication]currentNbOperations should set to 0 after update the shippedOpsRate
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-6624
>                 URL: https://issues.apache.org/jira/browse/HBASE-6624
>             Project: HBase
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 0.94.0
>            Reporter: terry zhang
>            Assignee: terry zhang
>         Attachments: jira-6624.patch
>
>
> now currentNbOperations will not reset to 0 and increase after replication start. Now this value is used for calculate shippedOpsRate. if it is not reset to 0 shippedOpsRate is not correct

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-6624) [Replication]currentNbOperations should set to 0 after update the shippedOpsRate

Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455796#comment-13455796 ] 

Michael Drzal commented on HBASE-6624:
--------------------------------------

This seems like a reasonable change.  You will need to rebase the patch as HBASE-6623 got committed, so you will need to move that down a line at the very least.  Unless I'm misreading the code.
                
> [Replication]currentNbOperations should set to 0 after update the shippedOpsRate
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-6624
>                 URL: https://issues.apache.org/jira/browse/HBASE-6624
>             Project: HBase
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 0.94.0
>            Reporter: terry zhang
>            Assignee: terry zhang
>         Attachments: jira-6624.patch
>
>
> now currentNbOperations will not reset to 0 and increase after replication start. Now this value is used for calculate shippedOpsRate. if it is not reset to 0 shippedOpsRate is not correct

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira