The standard deployment does setup some cleanup tasks that purges 'old'
data. This seems to be different from what you're asking though. What do
you imagine using as your "backup space" if not /dev/null?
On Tue, Jun 14, 2016 at 7:45 AM, Kuba Sienkiewicz
wrote:
> PS. I'm saying about automat
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/145
---
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 cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/145
+1 looks good
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/150
---
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 asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/148
---
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 nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/148
+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 project does not have this feature
enabled and wishes so, or if
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/148
+1. Good fix!
---
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 wishe
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/144
---
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 nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/145
ð
---
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
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/150
+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 project does not have this feature
enabled and wishes so, or if
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/145
Bump - anyone? Bueller?
@nickwallen - those changes you requested have been for a bit.
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/150
ð¯ - really solid work, Casey. Looks like it was a bear to track down.
I ran this in EC2 with
2 workers and 15 executors for 16 minutes - no error.
1 worker and 15
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/144
+1 this looks good
---
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 wi
You are correct that the Kibana 4 interface does not currently have a
dashboard that gets created automatically like the older Kibana 3
dashboard. I am actually working on that now per METRON-219;
https://issues.apache.org/jira/browse/METRON-219.
The link below is a fairly good introduction to us
GitHub user cestella opened a pull request:
https://github.com/apache/incubator-metron/pull/151
METRON-223: Invalid and Erroneous messages should go to kafka for further
analysis in the Parser Topology
Right now we send error messages and invalid messages to separate streams
in the
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/150
I don't see a difference in the clone method vs the method currently
implemented. I think we should evaluate in a follow-on JIRA whether any of the
clones are needed. It seems that none
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/150
Good deal on tracking this one down. Think it's worth switching back to the
.clone method in the BulkMessageWriterBolt?
---
If your project is set up for it, you can reply to this email
PS. I'm saying about automatically moving data away from hdfs to some sort
of backup space. Sorry for inaccuracy in previous email (removing).
wt., 14.06.2016 o 13:32 użytkownik Kuba Sienkiewicz
napisał:
> Hi all,
> I've tested metron for 2 days and I already have over 20GB of data (w/o
> any sp
Hi all,
I've tested metron for 2 days and I already have over 20GB of data (w/o any
special network traffic, server just stood untouched).
What are good practices with such big amounts of data that metron stores?
Also do metron support removing historical data automatically?
Best Regards,
Jakub Si
19 matches
Mail list logo
