[jira] [Updated] (METRON-322) Global Batching & flushing
[ https://issues.apache.org/jira/browse/METRON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Sirota updated METRON-322: Assignee: Matt Foley > Global Batching & flushing > -- > > Key: METRON-322 > URL: https://issues.apache.org/jira/browse/METRON-322 > Project: Metron > Issue Type: Improvement >Reporter: Ajay Yadav >Assignee: Matt Foley > > Flushing individual telemetries with disparate traffic are not only difficult > to tune in single topology but also creates lot of failed message overhead as > topology level configurations like “timeout, max.spout.pending” etc can’t be > changed for every telemetry. Instead of batching individual telemetries in > enrichment we should batch & flush them together. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (METRON-322) Global Batching & flushing
[ https://issues.apache.org/jira/browse/METRON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Sirota updated METRON-322: Assignee: (was: Ajay Yadav) > Global Batching & flushing > -- > > Key: METRON-322 > URL: https://issues.apache.org/jira/browse/METRON-322 > Project: Metron > Issue Type: Improvement >Reporter: Ajay Yadav > > Flushing individual telemetries with disparate traffic are not only difficult > to tune in single topology but also creates lot of failed message overhead as > topology level configurations like “timeout, max.spout.pending” etc can’t be > changed for every telemetry. Instead of batching individual telemetries in > enrichment we should batch & flush them together. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
