Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/149
I also went ahead and added a bit better logging if the CME returns, we
should get a sense of what the other threads are doing. Definitely would like
to see if you see any CMEs with the c
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/149
@dlyle65535 any chance you can run that again with this commit?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proj
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/149
Just for those poor souls who are debugging this on the internet, this is
the sister exception (from the other thread):
> 2016-06-10 13:34:44.687 b.s.util [ERROR] Async loop died!
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/149
So, that's the other side of the concurrent modification exception,
@dlyle65535. Somehow we are modifying the JSONObject message while it's
deserializing, like in
https://groups.google.c
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/149
Overall ran well. Increasing the indexWriter executors to 2 didn't create
the ConcurrentModificationException. Increasing the kafkaSpout executors to 2
gave me the following exception, b
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/147
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/149
+1 from me pending EC2 test
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enab
Github user james-sirota commented on the issue:
https://github.com/apache/incubator-metron/pull/149
+ 1from me. great job
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user iraghumitra commented on the issue:
https://github.com/apache/incubator-metron/pull/147
Corrected Ryan's apache id
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
ena
Github user iraghumitra commented on the issue:
https://github.com/apache/incubator-metron/pull/147
Corrected apache id of Ryan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
en
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/147
My apache id is incorrect. After @iraghumitra makes the change +1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user cestella opened a pull request:
https://github.com/apache/incubator-metron/pull/149
METRON-217: Found a grabbag of bugs
Doing some scale testing, I found a grabbag of bugs:
* The elasticsearch writer should allow multiple ES hosts to be passed in
via a List. This sho
12 matches
Mail list logo