You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2019/01/31 00:29:00 UTC

[jira] [Created] (HBASE-21813) ServerNotRunningYet exception should include machine-readable server name

Sergey Shelukhin created HBASE-21813:
----------------------------------------

             Summary: 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


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)