There were reports that workers with archived oplogs are not (or not always?) returned by the worker enumeration, but if they are interacted with, leading to new entries written to the primary oplog, they reappear.
This needs to be investigated / some new tests written, and fixed.
There were reports that workers with archived oplogs are not (or not always?) returned by the worker enumeration, but if they are interacted with, leading to new entries written to the primary oplog, they reappear.
This needs to be investigated / some new tests written, and fixed.