Closed jeromegn closed 2 years ago
Thanks a lot for the very detailed report!
There's nothing to worry about: this happens when the instance suspects another to be down and then learns that it wasn't down after all.
It was supposed to be a debug trace (then the span would contain useful metadata), sorry about the noise! I'll ship a patch release for this and close the issue when done.
We're using an fat identity with a bump.
and our Identity implementation:
We're handling members like:
I started listing foca members via
iter_members()
to try and debug this.Some logs I see when restarting:
Should we be worried about the
Member not found
log message or are these normal? They don't seem to appear repeatedly. This could be a race between 2 notifications?