SEZ9 commented on issue #13298:
URL: https://github.com/apache/seatunnel/issues/13298#issuecomment-6962277695

   Thanks for filing this as a separate follow-up to #13060. The scope and 
acceptance evidence are clear, and the existing per-writer cleanup should stay 
until a replacement proves equivalent fencing coverage.
   
   The design note already requested above is the next step, so I won't repeat 
those points. Two things would help alongside it:
   
   - If you have baseline numbers for the current behaviour (producer 
initializations and recovery time for a given writer count, retained history 
and retry count), please share them so that any reduction can be measured 
against them.
   - Implementation ownership is still open. Are you willing to write the 
design note and submit the PR once #13060 has merged or otherwise settled its 
final recovery contract?
   
   <!-- streview-comment:2412 -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to