[
https://issues.apache.org/jira/browse/HBASE-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HBASE-21813:
-------------------------------------
Description:
As far as I see, this exception is thrown before the start code of the
destination can be verified from the request on RS side; the code that handles
it (e.g. retries from open region procedure) use it to retry later on the same
server.
However, if the start code of the server that is not running is different from
the intended start code of the operation those retries are a waste of time.
The exception should include a server name with a start code (which it already
includes as part of the message in some cases), so that the caller could check
that.
was:
As far as I see, this exception is thrown before the start code of the
destination can be verified from the request on RS side; the code that handles
it (e.g. retries from open region procedure) use it to retry later on the same
server.
However, if the start code of the server that is not running is different from
the intended start code of the operations those retries are a waste of time.
The exception should include a server name with a start code (which it already
includes as part of the message in some cases), so that the caller could check
that.
> ServerNotRunningYet exception should include machine-readable server name
> -------------------------------------------------------------------------
>
> Key: HBASE-21813
> URL: https://issues.apache.org/jira/browse/HBASE-21813
> Project: HBase
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Priority: Major
>
> As far as I see, this exception is thrown before the start code of the
> destination can be verified from the request on RS side; the code that
> handles it (e.g. retries from open region procedure) use it to retry later on
> the same server.
> However, if the start code of the server that is not running is different
> from the intended start code of the operation those retries are a waste of
> time.
> The exception should include a server name with a start code (which it
> already includes as part of the message in some cases), so that the caller
> could check that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
