hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5618) SplitLogManager - prevent unnecessary attempts to resubmits
Date Sat, 07 Apr 2012 23:34:17 GMT

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

stack updated HBASE-5618:
-------------------------

       Resolution: Fixed
    Fix Version/s: 0.94.0
                   0.92.2
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Applied to 0.92, 0.94 and trunk.  Thanks for the patch Prakash.
                
> SplitLogManager - prevent unnecessary attempts to resubmits
> -----------------------------------------------------------
>
>                 Key: HBASE-5618
>                 URL: https://issues.apache.org/jira/browse/HBASE-5618
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal, zookeeper
>            Reporter: Prakash Khemani
>            Assignee: Prakash Khemani
>             Fix For: 0.92.2, 0.94.0
>
>         Attachments: 0001-HBASE-5618-SplitLogManager-prevent-unnecessary-attem.patch,
0001-HBASE-5618-SplitLogManager-prevent-unnecessary-attem.patch, 0001-HBASE-5618-SplitLogManager-prevent-unnecessary-attem.patch,
0001-HBASE-5618-SplitLogManager-prevent-unnecessary-attem.patch, 0001-HBASE-5618-SplitLogManager-prevent-unnecessary-attem.patch
>
>
> Currently once a watch fires that the task node has been updated (hearbeated) by the
worker, the splitlogmanager still quite some time before it updates the "last heard from"
time. This is because the manager currently schedules another getDataSetWatch() and only after
that finishes will it update the task's "last heard from" time.
> This leads to a large number of zk-BadVersion warnings when resubmission is continuously
attempted and it fails.
> Two changes should be made
> (1) On a resubmission failure because of BadVersion the task's lastUpdate time should
get upped.
> (2) The task's lastUpdate time should get upped as soon as the nodeDataChanged() watch
fires and without waiting for getDataSetWatch() to complete.

--
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

        

Mime
View raw message