Remove Streams max.poll.interval override
Since we now call poll during restore, we can decrease the timeout
to a reasonable value, which should help Streams make progress if
threads get stuck.
Reviewers: Guozhang Wang  Bill Bejeck
@@ -719,13 +719,6 @@ public class StreamsConfig extends AbstractConfig {
tempConsumerDefaultOverrides.put(ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "earliest");
tempConsumerDefaultOverrides.put(ConsumerConfig.ENABLE_AUTO_COMMIT_CONFIG, "false");
tempConsumerDefaultOverrides.put("internal.leave.group.on.close", false);
- // MAX_POLL_INTERVAL_MS_CONFIG needs to be large for streams to handle cases when
- // streams is recovering data from state stores. We may set it to Integer.MAX_VALUE since
- // the streams code itself catches most exceptions and acts accordingly without needing
- // this timeout. Note however that deadlocks are not detected (by definition) so we
- // are losing the ability to detect them by setting this value to large. Hopefully
- // deadlocks happen very rarely or never.
- tempConsumerDefaultOverrides.put(ConsumerConfig.MAX_POLL_INTERVAL_MS_CONFIG, Integer.toString(Integer.MAX_VALUE));
CONSUMER_DEFAULT_OVERRIDES = Collections.unmodifiableMap(tempConsumerDefaultOverrides);
}
