[jira] [Commented] (HBASE-30099) HRegionServer.getBootstrapNodes() NPE when GetBootstrapNodes RPC arrives during startup

["mazhengxuan (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-30099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18096811#comment-18096811 ] 

mazhengxuan commented on HBASE-30099:
-------------------------------------

{{I would like to work on this issue. I will look into the RegionServer startup path and the GetBootstrapNodes RPC handling, then prepare a PR if I can reproduce the NPE. If nobody is working on it, could someone assign it to me?}}

 

> HRegionServer.getBootstrapNodes() NPE when GetBootstrapNodes RPC arrives during startup
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-30099
>                 URL: https://issues.apache.org/jira/browse/HBASE-30099
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 3.0.0-beta-1, 2.6.5, 2.5.14
>            Reporter: Nick Dimiduk
>            Priority: Major
>
> {{HRegionServer.getBootstrapNodes()}} throws {{NullPointerException: Cannot invoke "BootstrapNodeManager.getBootstrapNodes()" because "this.bootstrapNodeManager" is null}} when the {{GetBootstrapNodes}} RPC arrives after the RPC server starts accepting connections but before {{preRegistrationInitialization()}} has assigned the field. Once tripped, every subsequent {{GetBootstrapNodes}} RPC on that instance returns the same NPE to the caller.
> Observed in production on a branch-2.6 cluster during a period of fleet-wide RS restarts, when peer RegionServers all issued bootstrap-node discovery against each fresh RS during its startup window. Same class of startup race as HBASE-28088.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)