akka/akka-core

Cluster 'self' status is 'Removed' before joining

Open

#25,663 opened on Sep 21, 2018

View on GitHub
 (1 comment) (3 reactions) (0 assignees)Scala (3,547 forks)batch import
1 - triagedhelp wantedt:cluster

Repository metrics

Stars
 (13,277 stars)
PR merge metrics
 (Avg merge 8d 19h) (10 merged PRs in 30d)

Description

When the current node is not part of the cluster gossip, the cluster status of 'self' is reported as Removed.

This has the effect that the initial cluster status, before joining, is also Removed. This used to be rare when joining based on seed-nodes from the configuration was common, but now with more sophisticated cluster bootstrap mechanisms it may become more common.

It might be nice to introduce an Uninitialized cluster state.

Contributor guide

Research direction
Inspect the file akka cluster/src/main/scala/akka/cluster/ClusterReadView.scala, specifically line 113 where 'self' cluster status is reported as Removed. Understand the cluster state lifecycle and consider adding a new 'Uninitialized' state to represent nodes that have not yet joined. Verify that the change is consistent with the cluster state machine and update tests accordingly.
Tech stack
scala
Domain
backenddistributed systems
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50