[jira] [Updated] (HBASE-9843) Various fixes in client code

2013-10-30 Thread Nicolas Liochon (JIRA)

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

Nicolas Liochon updated HBASE-9843:
---

  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

> Various fixes in client code
> 
>
> Key: HBASE-9843
> URL: https://issues.apache.org/jira/browse/HBASE-9843
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Affects Versions: 0.96.0
>Reporter: Nicolas Liochon
>Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9843-trunk.v2.patch, 9843-trunk.v3.patch
>
>
> This mainly fixes issues when we had "long" errors, for example a multi 
> blocked when trying to obtain a lock that was finally failing after 60s. 
> Previously we were trying only for 5 minutes. We now do all the tries. I've 
> fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 
> 20 tries we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not 
> in a very good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (HBASE-9843) Various fixes in client code

2013-10-25 Thread Nicolas Liochon (JIRA)

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

Nicolas Liochon updated HBASE-9843:
---

Status: Open  (was: Patch Available)

> Various fixes in client code
> 
>
> Key: HBASE-9843
> URL: https://issues.apache.org/jira/browse/HBASE-9843
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Affects Versions: 0.96.0
>Reporter: Nicolas Liochon
>Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9843-trunk.v2.patch, 9843-trunk.v3.patch
>
>
> This mainly fixes issues when we had "long" errors, for example a multi 
> blocked when trying to obtain a lock that was finally failing after 60s. 
> Previously we were trying only for 5 minutes. We now do all the tries. I've 
> fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 
> 20 tries we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not 
> in a very good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (HBASE-9843) Various fixes in client code

2013-10-25 Thread Nicolas Liochon (JIRA)

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

Nicolas Liochon updated HBASE-9843:
---

Status: Patch Available  (was: Open)

> Various fixes in client code
> 
>
> Key: HBASE-9843
> URL: https://issues.apache.org/jira/browse/HBASE-9843
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Affects Versions: 0.96.0
>Reporter: Nicolas Liochon
>Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9843-trunk.v2.patch, 9843-trunk.v3.patch
>
>
> This mainly fixes issues when we had "long" errors, for example a multi 
> blocked when trying to obtain a lock that was finally failing after 60s. 
> Previously we were trying only for 5 minutes. We now do all the tries. I've 
> fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 
> 20 tries we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not 
> in a very good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (HBASE-9843) Various fixes in client code

2013-10-25 Thread Nicolas Liochon (JIRA)

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

Nicolas Liochon updated HBASE-9843:
---

Attachment: 9843-trunk.v3.patch

> Various fixes in client code
> 
>
> Key: HBASE-9843
> URL: https://issues.apache.org/jira/browse/HBASE-9843
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Affects Versions: 0.96.0
>Reporter: Nicolas Liochon
>Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9843-trunk.v2.patch, 9843-trunk.v3.patch
>
>
> This mainly fixes issues when we had "long" errors, for example a multi 
> blocked when trying to obtain a lock that was finally failing after 60s. 
> Previously we were trying only for 5 minutes. We now do all the tries. I've 
> fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 
> 20 tries we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not 
> in a very good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (HBASE-9843) Various fixes in client code

2013-10-25 Thread Nicolas Liochon (JIRA)

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

Nicolas Liochon updated HBASE-9843:
---

Status: Patch Available  (was: Open)

> Various fixes in client code
> 
>
> Key: HBASE-9843
> URL: https://issues.apache.org/jira/browse/HBASE-9843
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Affects Versions: 0.96.0
>Reporter: Nicolas Liochon
>Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9843-trunk.v2.patch
>
>
> This mainly fixes issues when we had "long" errors, for example a multi 
> blocked when trying to obtain a lock that was finally failing after 60s. 
> Previously we were trying only for 5 minutes. We now do all the tries. I've 
> fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 
> 20 tries we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not 
> in a very good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (HBASE-9843) Various fixes in client code

2013-10-25 Thread Nicolas Liochon (JIRA)

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

Nicolas Liochon updated HBASE-9843:
---

Attachment: 9843-trunk.v2.patch

> Various fixes in client code
> 
>
> Key: HBASE-9843
> URL: https://issues.apache.org/jira/browse/HBASE-9843
> Project: HBase
>  Issue Type: Bug
>  Components: Client
>Affects Versions: 0.96.0
>Reporter: Nicolas Liochon
>Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9843-trunk.v2.patch
>
>
> This mainly fixes issues when we had "long" errors, for example a multi 
> blocked when trying to obtain a lock that was finally failing after 60s. 
> Previously we were trying only for 5 minutes. We now do all the tries. I've 
> fixed stuff around this area to make it work.
> There is also more logs.
> I've changed the back off array. With the default pause of 100ms, even after 
> 20 tries we still retry every 10s.
> I've also changed the max per RS to something minimal. If the cluster is not 
> in a very good state it's less aggressive. It seems to be a better default.
> I've done two tests:
>  - on a small; homogeneous cluster, I had the same performances
>  - on a bigger, but heterogeneous cluster it was twice as fast.



--
This message was sent by Atlassian JIRA
(v6.1#6144)