kdaectrl: aborting #46

Activity

1. rerpha

   changed the title [-]aborting[/-] [+]kdaectrl: aborting[/+] on May 14, 2026
2. rerpha

   transferred this issue fromISISComputingGroup/kafka_dae_controlon May 14, 2026
3. rerpha

   added this to the September 2026 milestone on May 14, 2026
4. Tom-Willemsen commented on May 19, 2026

   

   Tom-Willemsen

   on May 19, 2026

   Member

   More actions

   One option for discussion:

   • "abort" sends a runStop with a metadata flag that causes the filewriter to not write anything
   • "cancel abort" re-sends a runStart with the same run number/start time as the "aborted" run had (this should cause consumers to re-read the relevant events)
5. rerpha

   moved this to research/needs discussion in Data streaming for HRPD-X & SANDALS-IIon Jun 2, 2026
6. rerpha

   added this to Data streaming for HRPD-X & SANDALS-IIon Jun 2, 2026
7. rerpha

   moved this from research/needs discussion to Ready in Data streaming for HRPD-X & SANDALS-IIon Jul 14, 2026
8. rerpha commented on Jul 22, 2026

   

   rerpha

   on Jul 22, 2026

   Last edited by rerpha

   ContributorAuthor

   More actions

   One option for discussion:

   • "abort" sends a runStop with a metadata flag that causes the filewriter to not write anything
   • "cancel abort" re-sends a runStart with the same run number/start time as the "aborted" run had (this should cause consumers to re-read the relevant events)

   we should discuss whether "cancel abort" makes sense in the streaming context.

   Additionally whether it'd be easier to just create a separate schema or update the current run stop schema with an "abort" bool toggle. The latter is technically backwards compatible. On the hardware side all we probably need to do is stop the board from streaming.
9. rerpha

   self-assigned this

   on Aug 24, 2026
10. rerpha

    moved this from Ready to In progress in Data streaming for HRPD-X & SANDALS-IIon Aug 24, 2026