Tommy Becker created KAFKA-16018:
Summary: KafkaStreams can go into a zombie state if
UncaughtExceptionHandler is specified via the deprecated method
Key: KAFKA-16018
URL:
Tommy Becker created KAFKA-13197:
Summary: KStream-GlobalKTable join semantics don't match
documentation
Key: KAFKA-13197
URL: https://issues.apache.org/jira/browse/KAFKA-13197
Project: Kafka
Tommy Becker created KAFKA-10324:
Summary: Pre-0.11 consumers can get stuck when messages are
downconverted from V2 format
Key: KAFKA-10324
URL: https://issues.apache.org/jira/browse/KAFKA-10324
Tommy Becker created KAFKA-7700:
---
Summary: AbstractConfig does not honor Properties defaults
Key: KAFKA-7700
URL: https://issues.apache.org/jira/browse/KAFKA-7700
Project: Kafka
Issue Type:
Tommy Becker created KAFKA-6069:
---
Summary: Streams metrics tagged incorrectly
Key: KAFKA-6069
URL: https://issues.apache.org/jira/browse/KAFKA-6069
Project: Kafka
Issue Type: Bug
Tommy Becker created KAFKA-5379:
---
Summary: ProcessorContext.appConfigs() should return
parsed/validated values
Key: KAFKA-5379
URL: https://issues.apache.org/jira/browse/KAFKA-5379
Project: Kafka
Tommy Becker created KAFKA-5334:
---
Summary: rocksdb.config.setter must be a class instance, not a
class name
Key: KAFKA-5334
URL: https://issues.apache.org/jira/browse/KAFKA-5334
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013135#comment-16013135
]
Tommy Becker commented on KAFKA-5256:
-
Thinking about this some more, the scenario outlined above
[
https://issues.apache.org/jira/browse/KAFKA-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012738#comment-16012738
]
Tommy Becker commented on KAFKA-5256:
-
I noticed this originally when my state store directories were
[
https://issues.apache.org/jira/browse/KAFKA-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012736#comment-16012736
]
Tommy Becker commented on KAFKA-5256:
-
Well ideally it is idempotent yes, but consider the scenario
[
https://issues.apache.org/jira/browse/KAFKA-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011360#comment-16011360
]
Tommy Becker commented on KAFKA-5241:
-
I should also add that it seems broken that in the absence of
[
https://issues.apache.org/jira/browse/KAFKA-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommy Becker updated KAFKA-5241:
Fix Version/s: 0.11.0.0
Status: Patch Available (was: Open)
> GlobalKTable does not
Tommy Becker created KAFKA-5241:
---
Summary: GlobalKTable does not checkpoint offsets after restoring
state
Key: KAFKA-5241
URL: https://issues.apache.org/jira/browse/KAFKA-5241
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010389#comment-16010389
]
Tommy Becker commented on KAFKA-5241:
-
I have a patch for this and will take the issue, if someone can
[
https://issues.apache.org/jira/browse/KAFKA-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommy Becker resolved KAFKA-5044.
-
Resolution: Invalid
> max.in.flight.requests.per.connection > 1 is ineffective
>
[
https://issues.apache.org/jira/browse/KAFKA-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962742#comment-15962742
]
Tommy Becker commented on KAFKA-5044:
-
Thanks for the explanation; closing this issue.
>
[
https://issues.apache.org/jira/browse/KAFKA-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961534#comment-15961534
]
Tommy Becker commented on KAFKA-5042:
-
Apologies, I used the wrong issue number. Will close the above
Tommy Becker created KAFKA-5044:
---
Summary: max.in.flight.requests.per.connection > 1 is ineffective
Key: KAFKA-5044
URL: https://issues.apache.org/jira/browse/KAFKA-5044
Project: Kafka
Issue
Tommy Becker created KAFKA-5042:
---
Summary: InFlightRequests#isEmpty() always returns false
Key: KAFKA-5042
URL: https://issues.apache.org/jira/browse/KAFKA-5042
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708608#comment-15708608
]
Tommy Becker commented on KAFKA-4436:
-
FWIW, I would be in favor of doing this for all configs; it's
[
https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384017#comment-15384017
]
Tommy Becker commented on KAFKA-3915:
-
[~junrao] Yes I understand the max message size includes
[
https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355150#comment-15355150
]
Tommy Becker commented on KAFKA-3915:
-
Actually, I don't think this is true. The buffer is set to
[
https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15355135#comment-15355135
]
Tommy Becker commented on KAFKA-3915:
-
Should a change to the default maxMessageSize be considered?
Tommy Becker created KAFKA-3915:
---
Summary: LogCleaner IO buffers do not account for potential size
difference due to message format change
Key: KAFKA-3915
URL: https://issues.apache.org/jira/browse/KAFKA-3915
[
https://issues.apache.org/jira/browse/KAFKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15224928#comment-15224928
]
Tommy Becker commented on KAFKA-3499:
-
This was/is a problem in Samza as well. Though many classes may
[
https://issues.apache.org/jira/browse/KAFKA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14375884#comment-14375884
]
Tommy Becker commented on KAFKA-873:
I think it would be nice. The status of zkclient
Tommy Becker created KAFKA-1909:
---
Summary: VerifiableProperties does not see default properties of
the wrapped Properties instance
Key: KAFKA-1909
URL: https://issues.apache.org/jira/browse/KAFKA-1909
27 matches
Mail list logo
