View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000416010000-014: PubSubSpecpublic2018-02-17 17:572021-06-11 13:55
ReporterRandy Armstrong Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
Summary0004160: DataSetMessageSequenceNumber: What Happens on Crash?
Description

DataSetMessageSequenceNumber is a monotonically increasing number but what happens if the Publisher restarts/crashes?

Is the expectation that the last sequence number sent written to disk immediately? If not how does a Subscriber know that the SequenceNumber reset?

Recommendation: define 0 to mean the start of a new sequence. Subscribers assme all data to follow is new data. If a SequenceNumber rolls over it starts at 1.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

duplicate of 0004371 closedMatthias Damm PubSub DataSetMessageSequenceNumber jump handling 

Activities

Randy Armstrong

2018-02-20 16:40

administrator   ~0008882

Using 0 does not work because 0 message may be missed.

Update text in spec to explain options available to subscribers.

i.e. if old sequence check timestamp
if no timestamp ignore message but wait for timeout...

Matthias Damm

2021-06-09 19:12

developer   ~0014536

This was already fixed with 0004371 with adding the following clarification:
Subscribers shall discard the records they keep for sequence numbers if they do not receive messages for two times the keep alive time to deal with Publishers that are out of service and were not able to continue from the last used SequenceNumber.

Added additional clarification that the sequence number starts at 0.

Jim Luth

2021-06-11 13:55

administrator   ~0014551

Agreed to DUP in Virtual F2F.

Issue History

Date Modified Username Field Change
2018-02-17 17:57 Randy Armstrong New Issue
2018-02-20 16:40 Randy Armstrong Note Added: 0008882
2018-02-20 16:40 Randy Armstrong Assigned To => Matthias Damm
2018-02-20 16:40 Randy Armstrong Status new => assigned
2021-06-09 19:08 Matthias Damm Relationship added duplicate of 0004371
2021-06-09 19:12 Matthias Damm Status assigned => resolved
2021-06-09 19:12 Matthias Damm Resolution open => fixed
2021-06-09 19:12 Matthias Damm Note Added: 0014536
2021-06-11 13:54 Jim Luth Resolution fixed => duplicate
2021-06-11 13:55 Jim Luth Status resolved => closed
2021-06-11 13:55 Jim Luth Note Added: 0014551