hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16291) Explain the correct semantic of hbase.client.retries.number in doc
Date Wed, 27 Jul 2016 11:56:20 GMT

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

Phil Yang updated HBASE-16291:
------------------------------
    Description: 
In hbase-default.xml (and also in HBase Book), the description of hbase.client.retries.number
is:
{quote}
Maximum retries.  Used as maximum for all retryable operations such as the getting of a cell's
value, starting a row update, etc.  Retry interval is a rough function based on hbase.client.pause.
 At first we retry at this interval but then with backoff, we pretty quickly reach  retrying
every ten seconds.  See HConstants#RETRY_BACKOFF for how the backup ramps up.  Change this
setting and hbase.client.pause to suit your workload.
{quote}

However, the semantic of this conf is confusing and different in various branches. After HBASE-14521,
in master it means "the number of RETRIES", but in all the other branches it still means "the
number of TRIES".

So I think we need make the doc clear and tell users what it is in 0.98/1.x and what it will
be from 2.0

  was:
In hbase-default.xml (and also in HBase Book), the description of hbase.client.retries.number
is:
{quote}
Maximum retries.  Used as maximum for all retryable operations such as the getting of a cell's
value, starting a row update, etc.  Retry interval is a rough function based on hbase.client.pause.
 At first we retry at this interval but then with backoff, we pretty quickly reach  retrying
every ten seconds.  See HConstants#RETRY_BACKOFF for how the backup ramps up.  Change this
setting and hbase.client.pause to suit your workload.
{quote}

However, the semantic of this conf is confusing and different in various branches. After HBASE-14521,
in master it means "the number of RETRIES", but in all the other branches it still means "the
number of TRIES".

So I think we need make the doc clearly and tell users what it is in 0.98/1.x and what it
will be from 2.0


> Explain the correct semantic of hbase.client.retries.number in doc
> ------------------------------------------------------------------
>
>                 Key: HBASE-16291
>                 URL: https://issues.apache.org/jira/browse/HBASE-16291
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.1.5, 1.2.2, 0.98.20
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>         Attachments: HBASE-16291-v1.patch
>
>
> In hbase-default.xml (and also in HBase Book), the description of hbase.client.retries.number
is:
> {quote}
> Maximum retries.  Used as maximum for all retryable operations such as the getting of
a cell's value, starting a row update, etc.  Retry interval is a rough function based on hbase.client.pause.
 At first we retry at this interval but then with backoff, we pretty quickly reach  retrying
every ten seconds.  See HConstants#RETRY_BACKOFF for how the backup ramps up.  Change this
setting and hbase.client.pause to suit your workload.
> {quote}
> However, the semantic of this conf is confusing and different in various branches. After
HBASE-14521, in master it means "the number of RETRIES", but in all the other branches it
still means "the number of TRIES".
> So I think we need make the doc clear and tell users what it is in 0.98/1.x and what
it will be from 2.0



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

Mime
View raw message