Yes, I don't follow. Anyway, if the role of a member should be static (not
changed after startup/join) or dynamic (possible to change without restart)
is a question we are very interested in. We have discussed it. It's a lot
easier to implement the static role assignment, but we are curious to know
if there is a good real world use case for dynamic roles.

/Patrik

15 mar 2013 kl. 18:54 skrev Helena Edelson <notifications@github.com>:

In akka-cluster/src/main/scala/akka/cluster/ClusterDaemon.scala:

> -    case ClusterUserAction.Down(address)  => downing(address)
> -    case ClusterUserAction.Leave(address) => leaving(address)
> -    case Exit(address)                    => exiting(address)
> -    case Remove(address)                  => removing(address)
> -    case SendGossipTo(address)            => gossipTo(address)
> -    case msg: SubscriptionMessage         => publisher forward msg
> +    case msg: GossipEnvelope                    => receiveGossip(msg)
> +    case GossipTick                             => gossip()
> +    case ReapUnreachableTick                    => reapUnreachableMembers()
> +    case LeaderActionsTick                      => leaderActions()
> +    case PublishStatsTick                       => publishInternalStats()
> +    case InitJoin                               => initJoin()
> +    case JoinTo(address)                        => join(address)
> +    case ClusterUserAction.Join(address, roles) => joining(address, roles)
> +    case ClusterUserAction.Down(address)        => downing(address)
> +    case ClusterUserAction.Leave(address)       => leaving(address)

I guess since the node implicitly shuts down on leaving the cluster vs an
auto-join that is on/off for manually leaving the cluster but staying
operational, means my comment is moot. Disregard.

--
Reply to this email directly or view it on
GitHub<https://github.com/akka/akka/pull/1254/files#r3395995>
.