[jira] [Updated] (HBASE-13200) Improper configuration can leads to endless lease recovery during failover

2015-04-30 Thread Andrew Purtell (JIRA)

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

Andrew Purtell updated HBASE-13200:
---
Fix Version/s: 1.1.1
   1.2.0
   1.0.2
   0.98.13

Picked back to the 1.x branches and 0.98

 Improper configuration can leads to endless lease recovery during failover
 --

 Key: HBASE-13200
 URL: https://issues.apache.org/jira/browse/HBASE-13200
 Project: HBase
  Issue Type: Bug
  Components: MTTR
Reporter: He Liangliang
Assignee: He Liangliang
 Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1

 Attachments: HBASE-13200.patch


 When a node (DN+RS) has machine/OS level failure, another RS will try to do 
 lease recovery for the log file. It will retry for every 
 hbase.lease.recovery.dfs.timeout (default to 61s) from the second time. When 
 the hdfs configuration is not properly configured (e.g. socket connection 
 timeout) and without patch HDFS-4721, the lease recovery time can exceeded 
 the timeout specified by hbase.lease.recovery.dfs.timeout. This will lead to  
 endless retries and preemptions until the final timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-13200) Improper configuration can leads to endless lease recovery during failover

2015-03-18 Thread Liu Shaohui (JIRA)

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

Liu Shaohui updated HBASE-13200:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Thanks for the patch. [~heliangliang]

 Improper configuration can leads to endless lease recovery during failover
 --

 Key: HBASE-13200
 URL: https://issues.apache.org/jira/browse/HBASE-13200
 Project: HBase
  Issue Type: Bug
  Components: MTTR
Reporter: He Liangliang
Assignee: He Liangliang
 Fix For: 2.0.0

 Attachments: HBASE-13200.patch


 When a node (DN+RS) has machine/OS level failure, another RS will try to do 
 lease recovery for the log file. It will retry for every 
 hbase.lease.recovery.dfs.timeout (default to 61s) from the second time. When 
 the hdfs configuration is not properly configured (e.g. socket connection 
 timeout) and without patch HDFS-4721, the lease recovery time can exceeded 
 the timeout specified by hbase.lease.recovery.dfs.timeout. This will lead to  
 endless retries and preemptions until the final timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-13200) Improper configuration can leads to endless lease recovery during failover

2015-03-18 Thread Liu Shaohui (JIRA)

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

Liu Shaohui updated HBASE-13200:

Fix Version/s: 2.0.0

 Improper configuration can leads to endless lease recovery during failover
 --

 Key: HBASE-13200
 URL: https://issues.apache.org/jira/browse/HBASE-13200
 Project: HBase
  Issue Type: Bug
  Components: MTTR
Reporter: He Liangliang
Assignee: He Liangliang
 Fix For: 2.0.0

 Attachments: HBASE-13200.patch


 When a node (DN+RS) has machine/OS level failure, another RS will try to do 
 lease recovery for the log file. It will retry for every 
 hbase.lease.recovery.dfs.timeout (default to 61s) from the second time. When 
 the hdfs configuration is not properly configured (e.g. socket connection 
 timeout) and without patch HDFS-4721, the lease recovery time can exceeded 
 the timeout specified by hbase.lease.recovery.dfs.timeout. This will lead to  
 endless retries and preemptions until the final timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-13200) Improper configuration can leads to endless lease recovery during failover

2015-03-12 Thread He Liangliang (JIRA)

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

He Liangliang updated HBASE-13200:
--
Attachment: HBASE-13200.patch

Added linear backoff to avoid this.

 Improper configuration can leads to endless lease recovery during failover
 --

 Key: HBASE-13200
 URL: https://issues.apache.org/jira/browse/HBASE-13200
 Project: HBase
  Issue Type: Bug
  Components: MTTR
Reporter: He Liangliang
Assignee: He Liangliang
 Attachments: HBASE-13200.patch


 When a node (DN+RS) has machine/OS level failure, another RS will try to do 
 lease recovery for the log file. It will retry for every 
 hbase.lease.recovery.dfs.timeout (default to 61s) from the second time. When 
 the hdfs configuration is not properly configured (e.g. socket connection 
 timeout) and without patch HDFS-4721, the lease recovery time can exceeded 
 the timeout specified by hbase.lease.recovery.dfs.timeout. This will lead to  
 endless retries and preemptions until the final timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-13200) Improper configuration can leads to endless lease recovery during failover

2015-03-11 Thread He Liangliang (JIRA)

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

He Liangliang updated HBASE-13200:
--
Status: Patch Available  (was: Open)

 Improper configuration can leads to endless lease recovery during failover
 --

 Key: HBASE-13200
 URL: https://issues.apache.org/jira/browse/HBASE-13200
 Project: HBase
  Issue Type: Bug
  Components: MTTR
Reporter: He Liangliang
Assignee: He Liangliang
 Attachments: HBASE-13200.patch


 When a node (DN+RS) has machine/OS level failure, another RS will try to do 
 lease recovery for the log file. It will retry for every 
 hbase.lease.recovery.dfs.timeout (default to 61s) from the second time. When 
 the hdfs configuration is not properly configured (e.g. socket connection 
 timeout) and without patch HDFS-4721, the lease recovery time can exceeded 
 the timeout specified by hbase.lease.recovery.dfs.timeout. This will lead to  
 endless retries and preemptions until the final timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)