Github user nickwallen commented on a diff in the pull request: https://github.com/apache/metron/pull/1239#discussion_r226720064 --- Diff: metron-platform/metron-writer/src/main/java/org/apache/metron/writer/BulkWriterComponent.java --- @@ -118,12 +119,18 @@ public void commit(BulkWriterResponse response) { public void error(String sensorType, Throwable e, Iterable<Tuple> tuples, MessageGetStrategy messageGetStrategy) { LOG.error(format("Failing %d tuple(s); sensorType=%s", Iterables.size(tuples), sensorType), e); - MetronError error = new MetronError() - .withSensorType(Collections.singleton(sensorType)) - .withErrorType(Constants.ErrorType.INDEXING_ERROR) - .withThrowable(e); - tuples.forEach(t -> error.addRawMessage(messageGetStrategy.get(t))); - handleError(tuples, error); + tuples.forEach(t -> { + MetronError error = new MetronError() + .withSensorType(Collections.singleton(sensorType)) + .withErrorType(Constants.ErrorType.INDEXING_ERROR) + .withThrowable(e) + .addRawMessage(messageGetStrategy.get(t)); --- End diff -- While testing this, I am seeing a problem. I am trying to decide whether we should call that a pre-existing condition and fix that problem after this PR goes in or whether the change here makes things any worse. Let me know what you think. I have described the problem in [METRON-1832](https://issues.apache.org/jira/browse/METRON-1832). If any index destination goes down, error messages are continually recycled and grow larger and larger. In addition, long sequence of escape characters are created.
---