Benjamin Allan

@tom95858 forgot to tag you on the original question.

@oceandlr the usual timestamping applies. WRT alignment, the usual cases in which this patch will be active (L2 network blockage or monitored cluster is down) will preserve the alignment of...

I can modify the patch so that a default-off option enables the new behavior. Would that be satisfactory? A very simplified explanation of the driving cases is that at high...

marking as draft until done converting patch so that the old behavior remains the default and the test scripts are included.

@tom95858 I added a test of rollempty and changed the default value of the parameter to preserve the current behavior per discussion with @oceandlr. ready to go.

@tom95858 With this change, you still see the empty rollover files by default and we can suppress them in if we want to. Yes, we have experienced massive undesired, unnecessary...

@aamirrashid If this issue is still of interest, please comment. If not please let us know so we can close it. Generally, regarding v4 genders: - maestro (yaml-based) configuration is...

@nichamon I've seen it quite regularly, so when that cluster come's back up next week, I should be able to post a reproducer configuration and a useful suppression file that...

@tom95858 can you comment on the feasibility of supporting the use case above in the next major version or as a patch on v4? I would imagine defining a listening...

So will the ogc munge extension work in progress in some way enable the scenario where L2 and its local munge is not in on the secret of the munge...