Ticket #213 (new defect)

Opened 8 years ago

archman won't work if future time-stamped packets get seen

Reported by: paulf Owned by:
Priority: major Milestone: All Platforms
Component: archman Version: 7.6
Keywords: Cc:


The design of archman is slightly flawed in that if ANY packet in the poll of the ring has a future time-stamped packet and it is the packet that lands as the last check in its poll for the NEWEST data timestamp, you are basically screwed.

What archman will do then is run a number of waveman2disk pulls until that future timestamp is reached and then just sit there waiting.

The interim solution is to use Lynn's wftimefilter program to cleanse the ring...The real solution is to fix this broken logic to check for wildly jumpy time stamps and ALSO to look at the SNCL of the NEWEST data to see if it is even a packet the user configured to care about....or better yet, look at the average of end-times in a getmenu poll from the wave server being used....that would tell you if data have advanced into the storage medium to the point where a pull should be performed......

Note: See TracTickets for help on using tickets.