[jira] [Assigned] (HBASE-5618) SplitLogManager - prevent unnecessary attempts to resubmits
[ https://issues.apache.org/jira/browse/HBASE-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Khemani reassigned HBASE-5618: -- Assignee: Prakash Khemani 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 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
[jira] [Assigned] (HBASE-5326) splitlogmanager zk async handlers after shutdown
[ https://issues.apache.org/jira/browse/HBASE-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Khemani reassigned HBASE-5326: -- Assignee: Prakash Khemani splitlogmanager zk async handlers after shutdown Key: HBASE-5326 URL: https://issues.apache.org/jira/browse/HBASE-5326 Project: HBase Issue Type: Improvement Reporter: Prakash Khemani Assignee: Prakash Khemani The zk async handlers in SpltLogManager should ignore all callbacks after SplitLogManager has shutdown. Will make the test logs less noisy. -- 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] [Assigned] (HBASE-4997) SplitLogManager can have a race on batch.installed
[ https://issues.apache.org/jira/browse/HBASE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Khemani reassigned HBASE-4997: -- Assignee: Prakash Khemani SplitLogManager can have a race on batch.installed -- Key: HBASE-4997 URL: https://issues.apache.org/jira/browse/HBASE-4997 Project: HBase Issue Type: Bug Reporter: Prakash Khemani Assignee: Prakash Khemani This is a continuation of HBASE-4987. Will put up a patch shortly. -- 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] [Assigned] (HBASE-4967) connected client thrift sockets should have a server side read timeout
[ https://issues.apache.org/jira/browse/HBASE-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Khemani reassigned HBASE-4967: -- Assignee: Prakash Khemani connected client thrift sockets should have a server side read timeout -- Key: HBASE-4967 URL: https://issues.apache.org/jira/browse/HBASE-4967 Project: HBase Issue Type: Improvement Reporter: Prakash Khemani Assignee: Prakash Khemani If there is no socket read timeout and if the Thrift server is a ThreadPoolServer then server side threads will be used up waiting for dead unresponsive clients. -- 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] [Assigned] (HBASE-4932) Block cache can be mistakenly instantiated by tools
[ https://issues.apache.org/jira/browse/HBASE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Khemani reassigned HBASE-4932: -- Assignee: Prakash Khemani Block cache can be mistakenly instantiated by tools --- Key: HBASE-4932 URL: https://issues.apache.org/jira/browse/HBASE-4932 Project: HBase Issue Type: Bug Reporter: Prakash Khemani Assignee: Prakash Khemani Map Reduce tasks that create a writer to write HFiles inadvertently end up creating block cache. -- 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
