-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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.
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
Flush jitter causes input collection to freeze #2262
Comments
it's not freezing collection, it's just taking that long because your jitter is very high why would you need to do this? |
I don't really need to do this, but why would flush_jitter cause the inputs also to wait? |
oh, sorry I misread that, it shouldn't be happening that way what do you have collection_jitter set to? can you provide a full config file so I can reproduce? |
I usually have collection_jitter set to 0. I think any config file should work with the settings I described.
|
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes #2262
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes #2262
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes #2262
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes #2262
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes influxdata#2262
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes influxdata#2262
doing this unblocks incoming metrics while waiting for a flush to take place. we have to create a semaphore so that we can 'skip' flushes that try to run while a flush is already running. closes #2262
During my tests it looks like flush_jitter causes input plugins to freeze the collection.
To reproduce this quickly is rather easy:
I could reproduce this on version 1.1.x and in the master branch.
Actual behavior
Error messages like:
E! ERROR: input [inputs.cpu] took longer to collect than collection interval (10s)
And debug messages like:
D! Input [inputs.cpu] gathered metrics, (10s interval) in 33.689740435s
Expected behavior
Collection should work as usual, flush should be handled accordingly with the jitter delay
The text was updated successfully, but these errors were encountered: