Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/453
> I guess I'm ok with adding a new topology, but it's added a fair amount
of complexity to this JIRA and I'm not sure I buy that indexing errors (what
should be a rare event, IMO, in a healthy set of topologies) would materially
change how we tune the indexing topology...
I agree with @cestella here. I think by default we should have a single
indexing topology, for errors and everything else.
We should be able to make the code configurable enough, so that if a user
runs into performance issues caused by indexing telemetry and errors in the
same topology, they can easily deploy a second indexing topology that is
dedicated to indexing the errors.
This would give them the flexibility that @merrimanr was going for when
they need it. But that should be a non-default, "advanced" configuration of
Metron.
---
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 feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
