Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Idle Barrier is dropping all messages when source has clock offset #1710

Closed
sputnik13 opened this issue Dec 5, 2017 · 0 comments
Closed

Idle Barrier is dropping all messages when source has clock offset #1710

sputnik13 opened this issue Dec 5, 2017 · 0 comments

Comments

@sputnik13
Copy link
Contributor

The problem scenario is as follows

  • data stream is provided by an external source
  • the source clock has a negative offset relative to the kapacitor host
  • source is emitting data using its own clock
  • the source stops emitting data
  • idle barrier start emitting a barrier using kapacitor host clock
  • the source resumes emitting data using its local clock
  • last idle barrier time is ahead of source time thus data from source is dropped
sputnik13 added a commit to sputnik13/kapacitor that referenced this issue Dec 5, 2017
@sputnik13
make idle barrier time relative to messages
47451bc 
addresses influxdata#1710

By having barrier time be based on last (point | barrier) time + idle,
the desired behavior of idle barrier for handling no data (silence)
scenarios works even when the data source clock is offset from the
kapacitor host clock.
@sputnik13 sputnik13 mentioned this issue Dec 5, 2017
Merged
5 tasks
@sputnik13 sputnik13 changed the title Idle Barrier is dropping all messages from a stream Idle Barrier is dropping all messages when source has clock offset Dec 5, 2017
sputnik13 added a commit to sputnik13/kapacitor that referenced this issue Dec 5, 2017
@sputnik13
make idle barrier time relative to messages
529c1f7 
addresses influxdata#1710

By having barrier time be based on last (point | barrier) time + idle,
the desired behavior of idle barrier for handling no data (silence)
scenarios works even when the data source clock is offset from the
kapacitor host clock.
fdhex pushed a commit to fdhex/kapacitor that referenced this issue Jun 12, 2018
@sputnik13 @floriandudouet-swisscom
make idle barrier time relative to messages
73cf7eb 
addresses influxdata#1710

By having barrier time be based on last (point | barrier) time + idle,
the desired behavior of idle barrier for handling no data (silence)
scenarios works even when the data source clock is offset from the
kapacitor host clock.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sputnik13