Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 5 Apr 2012 00:15:18 +0000 (UTC)
From: "Prakash Khemani (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <311689308.15044.1333584918791.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2043595970.2932.1332434422335.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-5618) SplitLogManager - prevent unnecessary
 attempts to resubmits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Prakash Khemani updated HBASE-5618:
-----------------------------------

    Status: Open  (was: Patch Available)
    
> 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
>         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
>
>
> 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