{:timestamp=>"2015-12-07T16:37:58.521000-0500", :message=>"Exception in filterworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.", "exception"=>#<RuntimeError: can't add a new key into hash during iteration>, "backtrace"=>["org/jruby/RubyHash.java:992:in []='", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-filter-throttle-2.0.2/lib/logstash/filters/throttle.rb:186:infilter'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.1.0-java/lib/logstash/filters/base.rb:151:in multi_filter'", "org/jruby/RubyArray.java:1613:ineach'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.1.0-java/lib/logstash/filters/base.rb:148:in multi_filter'", "(eval):2597:incond_func_119'", "org/jruby/RubyArray.java:1613:in each'", "(eval):2594:incond_func_119'", "(eval):2620:in cond_func_112'", "org/jruby/RubyArray.java:1613:ineach'", "(eval):2608:in cond_func_112'", "(eval):804:infilter_func'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.1.0-java/lib/logstash/pipeline.rb:243:in filterworker'", "/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-core-2.1.0-java/lib/logstash/pipeline.rb:177:instart_filters'"], :level=>:error}
Well, did you check your filter configuration?
Well worked fine for 2 weeks ... Logstash just stopped and that was the error in the logs. I started the logstash and start working again. I wonder what happened ? Why logstash just stopped?
Hard to say without seeing your config. Has something to do with the way you use the throttle filter, evidently.