[BugFix] Fix find master NPE bug when starting FE from cluster snapshot

[gengjun-git]

Why I'm doing:

Set selfNode to alive, because the init of ReplicationGroupAdmin only collect the alive frontends node. The reason this bug doesn't always appear is that HeartBeatMgr also sets selfNode to alive, but this is asynchronous and depends on how fast HeartBeatMgr runs.

What I'm doing:

Fixes

[StarRocksFE.start():210] StarRocksFE start failed
java.lang.NullPointerException: null
        at com.sleepycat.je.rep.util.ReplicationGroupAdmin.getMasterSocket(ReplicationGroupAdmin.java:191) ~[starrocks-bdb-je-18.3.20.jar:?]
        at com.sleepycat.je.rep.util.ReplicationGroupAdmin.doMessageExchange(ReplicationGroupAdmin.java:607) ~[starrocks-bdb-je-18.3.20.jar:?]
        at com.sleepycat.je.rep.util.ReplicationGroupAdmin.getGroup(ReplicationGroupAdmin.java:406) ~[starrocks-bdb-je-18.3.20.jar:?]
        at com.starrocks.ha.BDBHA.removeNodeIfExist(BDBHA.java:219) ~[starrocks-fe.jar:?]
        at com.starrocks.server.NodeMgr.addFrontend(NodeMgr.java:791) ~[starrocks-fe.jar:?]
        at com.starrocks.lake.snapshot.RestoreClusterSnapshotMgr.updateFrontends(RestoreClusterSnapshotMgr.java:207) ~[starrocks-fe.jar:?]
        at com.starrocks.lake.snapshot.RestoreClusterSnapshotMgr.finishRestoring(RestoreClusterSnapshotMgr.java:93) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.start(StarRocksFE.java:199) ~[starrocks-fe.jar:?]
        at com.starrocks.StarRocksFE.main(StarRocksFE.java:99) ~[starrocks-fe.jar:?]

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.5
  • 3.4
  • 3.3

[sonarqubecloud]

Quality Gate failed

Failed conditions
D Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 1 / 1 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/server/NodeMgr.java	1	1	100.00%	[]

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)