-
Notifications
You must be signed in to change notification settings - Fork 490
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
kapacitor kept restarting with mutiple stateDuration (kapacitor 1.3.0~beta2) #1369
Comments
That's really odd that it just exits without displaying any error. If you run it by hand, does it display anything different? Does |
@wshi5985 I think I have been able to reproduce the issue. Running the task above with about 1000 writes per second, I can see a steady increase in RAM usage of Kapacitor. My guess is that the Linux oom killer is killing the Kapacitor process. I am looking into what causes the increased RAM usage. Can you confirm that you are also seeing a steady increase in RAM usage while the task is running? |
I may have spoken too soon. After letting the test run for several hours, the RAM usage has leveled out and is constant. It too longer than expected to reach the steady state but it has. @wshi5985 Maybe there isn't enough RAM available for it to reach steady state? Or this could be totally unrelated to a RAM issue. Anymore details you can provide would be much appreciated. |
I checked the memory usage , we have 4G memory, and only half are used. I don't see obvious memory usage increase. when it crashed every 15-20 min, the config was a little different, I changed to the config above, now it crashes every a few hours. this was the config when it crashed every 15-20 min: response_data response_data response_data |
And this is the config which has crash every a few hours var response_data = stream response_data response_data response_data response_data |
the only error i see from logs are lot of error like this [vip_test:alert9] 2017/05/10 14:03:28 E! error evaluating expression for level CRITICAL: no field or tag exists for responsetime_events_duration [vip_test:alert8] 2017/05/09 22:58:49 E! error evaluating expression for level CRITICAL: no field or tag exists for httpcode_events_duration resultstatus_events_duration |
any update on this issue ? thanks. [run] 2017/05/14 19:49:42 I! Kapacitor starting, version 1.3.0 |
Trying to reproduce this issue on current code base (v1.3.0-rc2) after couple of minutes I got a crash Version: compiled from master branch (last commit: 74fc18b) Configuration that I've used for this:
kapacitord output:
Thanks! |
with binary in #1380 , I don't see crash for 24 hours so far, but the stateDuration does not fully function now. from httpOut i can see response time are always above threshold , but it doesnot trigger any alert
|
@wshi5985 Thanks for testing out the PR in #1380! As for the current issue I think its a simple typo in the TICKscript. Try this edit:
|
Thanks, @nathanielc, It starts alerting now. |
@wshi5985 Thanks for the detailed reports. Looks like we have this fixed. |
when we use one stateDuration in data stream, it works fine, but if check multiple event's stateDuration with same data stream, kapacitor kept restarting.
The text was updated successfully, but these errors were encountered: