[
https://issues.apache.org/jira/browse/METRON-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875020#comment-15875020
]
ASF GitHub Bot commented on METRON-694:
---------------------------------------
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.
> Index Errors from Topologies
> ----------------------------
>
> Key: METRON-694
> URL: https://issues.apache.org/jira/browse/METRON-694
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
>
> Need to make sure (and review) that all the bolts write into the error queue.
> Errors should then be consumed from the error queue and indexed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
