Comment 6 for bug 1795212

Questions to follow up based on the discussions during drivers meeting on October 26th:
1. amotoki: what kind of corner cases and negative behaviors could happen (even with full sync)?
2. slaweq: in some (very) old releases rpc queues which agent's registered had some random id, so when agent was e.g. restarted it created new queue and would not consume messages from this old one.
AR: To double check slaweq's statement and clarify failure modes in question, i.e., what actually happens, together w/ Q1.
3. haleyb: doing it without a config option somehow? e.g. Resource queue with ExclusiveResourceProcessor used in L3 agent