I'm not sure that ID needs to be shared between cluster nodes, as I'm not even sure that it makes sense for the counter to be shared either. I think it is perfectly fine for each cluster node to do its round robin un-aware of the other one. 

Having said that, any IdentifiableDynamicRouteResolver can (when appropriate)  return a meaningful that is not an auto-generated one. All ASR route resolvers implement IdentifiableDynamicRouteResolver so in the particular case of ASR it is not an issue. Altho the state of each round robin is held individually at each cluster node.

Do you know of any particular use-case scenarios in which the user can benefit from the round robin state to be shared across an entire cluster?