I've changed back to persist mode, which is where I started at. If
syncrepl is not suited to large scale deployments/deployments with
frequent updates, does this mean the various ITS's against slurpd will
be dropped back into the queue to be fixed, instead of suspended?
First, I note, there is no "queue to be fixed". I did move
a number of ITS from Historic to Incoming, but left them
Suspended. I might later move some of them to Software Bugs.
Of course, whether or not the reports are eventually addressed
has little to do with the categorization or status of the ITS.
Developers contribute per their own desires.
Second, we just started this Syncrepl experiment. I suspect
Syncrepl will prove to be better than the slurpd approach
in almost all deployments. I also suspect that some deployments
will need a far more sophisticated replication engine than either
syncrepl and slurpd provide.