What is the real semantic of the parameter "hbase.client.retries.number"

[shixing <pa...@gmail.com>]

I have seen there are serveral use of the parameter "*
hbase.client.retries.number*" to be used.

And I find some cases used like this:
*for (int i =0; i < hbase.client.retries.number; i++) {*
*    doSomething();*
*}*

And in *doSomething() *there are also *hbase.client.retries.number* retries,
so the total retry are totally *
hbase.client.retries.number*hbase.client.retries.number*

For examples:
The HBaseAdmin's constructor, there are retries outof getMaster(), also
there are retries in the getMaster().

I see the trunk has changed, in the 0.94 branch, the retries num = *
hbase.client.retries.number*hbase.client.retries.number *logic still
exists. Should we fix it?


-- 
Best wishes!
My Friend~

Fwd: What is the real semantic of the parameter "hbase.client.retries.number"

[shixing <pa...@gmail.com>]

send to user@hbase.apache.org

---------- Forwarded message ----------
From: shixing <pa...@gmail.com>
Date: Thu, Jun 28, 2012 at 12:25 PM
Subject: What is the real semantic of the parameter
"hbase.client.retries.number"
To: hbase-user@hadoop.apache.org, dev@hbase.apache.org


I have seen there are serveral use of the parameter "*
hbase.client.retries.number*" to be used.

And I find some cases used like this:
*for (int i =0; i < hbase.client.retries.number; i++) {*
*    doSomething();*
*}*

And in *doSomething() *there are also *hbase.client.retries.number* retries,
so the total retry are totally *
hbase.client.retries.number*hbase.client.retries.number*

For examples:
The HBaseAdmin's constructor, there are retries outof getMaster(), also
there are retries in the getMaster().

I see the trunk has changed, in the 0.94 branch, the retries num = *
hbase.client.retries.number*hbase.client.retries.number *logic still
exists. Should we fix it?


-- 
Best wishes!
My Friend~



-- 
Best wishes!
My Friend~