I am currently trying out various ways in scaling services using axon
framework 4.12.
The latest iteration of that development is a pre warmed local database
per service instance that only has to process the events that occurred
between the creation of the projection database and newer events.
As the tracking event processor used is identical per service instance,
the server displays a “Duplicated segment claim detected” warning in the UI.
Of course this was a non issue when the services started their event
processing ‘fresh’, but I also found no easy way to manipulate the
token on service start, e.g. clone it with the others tokens position.
Do I understand correctly that this would be an issue if the instances
would SHARE their databases, as they would ‘steal’ each other claims?
With my setup, each service is ‘unaware’ of the other tracking token and
is manipulating its own database.
My main question is, can this warning be safely ignored, or are there
any additional adverse effects that can occur on axon server side,
I might not be aware of ?