[
https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5273:
Status: Patch Available (was: In Progress)
> KafkaConsumer.committed() should get latest committed
[
https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-5273 started by Apurva Mehta.
---
> KafkaConsumer.committed() should get latest committed offsets from the server
> -
[
https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5128:
Status: Patch Available (was: Open)
> TransactionCoordinator - Check inter broker protocol and mess
[
https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5128:
Labels: exactly-once (was: )
> TransactionCoordinator - Check inter broker protocol and message for
[
https://issues.apache.org/jira/browse/KAFKA-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5280:
Status: Patch Available (was: Open)
> Protect concurrent access to the cached transaction status
>
[
https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5247:
Status: Patch Available (was: Open)
> Consumer GroupCoordinator should continue to materialize comm
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5269:
Status: Patch Available (was: Open)
> TransactionBounceTest occasionally fails due to partition err
Apurva Mehta created KAFKA-5284:
---
Summary: Add tools and metrics to diagnose problems with the
idempotent producer and transactions
Key: KAFKA-5284
URL: https://issues.apache.org/jira/browse/KAFKA-5284
Apurva Mehta created KAFKA-5283:
---
Summary: Update clients and server code to make sure that epoch
and sequence numbers wrap around
Key: KAFKA-5283
URL: https://issues.apache.org/jira/browse/KAFKA-5283
P
[
https://issues.apache.org/jira/browse/KAFKA-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5147:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> KafkaProducer's TransactionManager nee
[
https://issues.apache.org/jira/browse/KAFKA-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5147:
Labels: exactly-once (was: )
Priority: Blocker (was: Major)
Fix Version/s: 0.11
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016496#comment-16016496
]
Apurva Mehta commented on KAFKA-5269:
-
It turns out that the `UNKNOWN_TOPIC_OR_PARTITI
Apurva Mehta created KAFKA-5282:
---
Summary: Transactions integration test: Use factory methods to
keep track of open producers and consumers and close them all on tearDown
Key: KAFKA-5282
URL: https://issues.apache.o
[
https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5281:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> System tests for KIP-98 / transactions
[
https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5281:
Priority: Blocker (was: Major)
> System tests for KIP-98 / transactions
> -
[
https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5281:
Summary: System tests for KIP-98 / transactions (was: System tests for
KIP-98 / transaction)
> Sys
Apurva Mehta created KAFKA-5281:
---
Summary: System tests for KIP-98 / transaction
Key: KAFKA-5281
URL: https://issues.apache.org/jira/browse/KAFKA-5281
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5279:
---
Assignee: Damian Guy (was: Guozhang Wang)
> TransactionCoordinator must expire transactional
[
https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5273:
---
Assignee: Apurva Mehta
> KafkaConsumer.committed() should get latest committed offsets from t
[
https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5273:
Priority: Blocker (was: Major)
> KafkaConsumer.committed() should get latest committed offsets from
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5269:
Priority: Blocker (was: Major)
> TransactionBounceTest occasionally fails due to partition errors
>
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5269:
Labels: exactly-once (was: )
> TransactionBounceTest occasionally fails due to partition errors
> -
[
https://issues.apache.org/jira/browse/KAFKA-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5270:
Priority: Blocker (was: Major)
> TransactionManager should send and `AddOffsetsToTxn` request only
[
https://issues.apache.org/jira/browse/KAFKA-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5270:
Priority: Major (was: Blocker)
> TransactionManager should send and `AddOffsetsToTxn` request only
[
https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5260:
---
Assignee: Damian Guy
> Producer should not send AbortTxn unless transaction has actually begu
[
https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5260:
Priority: Blocker (was: Critical)
> Producer should not send AbortTxn unless transaction has actual
[
https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5260:
Priority: Critical (was: Major)
> Producer should not send AbortTxn unless transaction has actually
[
https://issues.apache.org/jira/browse/KAFKA-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5259:
Labels: exactly-once (was: )
> TransactionalId authorization should imply ProducerId authorization
[
https://issues.apache.org/jira/browse/KAFKA-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5259:
Priority: Blocker (was: Major)
> TransactionalId authorization should imply ProducerId authorizatio
[
https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5032:
---
Assignee: Apurva Mehta
> Think through implications of max.message.size affecting record batc
[
https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5093:
Priority: Critical (was: Major)
> Load only batch header when rebuilding producer ID map
>
[
https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5202:
---
Assignee: Guozhang Wang
> Handle topic deletion for ongoing transactions
> --
[
https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5247:
Priority: Blocker (was: Major)
> Consumer GroupCoordinator should continue to materialize committed
[
https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5202:
Priority: Blocker (was: Major)
> Handle topic deletion for ongoing transactions
> -
[
https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5247:
---
Assignee: Apurva Mehta
> Consumer GroupCoordinator should continue to materialize committed o
[
https://issues.apache.org/jira/browse/KAFKA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5186:
Labels: exactly-once (was: )
> Avoid expensive initialization of producer state when upgrading
> --
[
https://issues.apache.org/jira/browse/KAFKA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5186:
Priority: Blocker (was: Critical)
> Avoid expensive initialization of producer state when upgrading
[
https://issues.apache.org/jira/browse/KAFKA-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016152#comment-16016152
]
Apurva Mehta commented on KAFKA-5033:
-
A default of `MAX_INT` seems reasonable here.
[
https://issues.apache.org/jira/browse/KAFKA-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5033:
Priority: Blocker (was: Major)
> Reconsider default retries for idempotent producer
> -
[
https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5032:
Labels: exactly-once (was: )
> Think through implications of max.message.size affecting record batc
[
https://issues.apache.org/jira/browse/KAFKA-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5030:
Labels: exactly-once (was: )
> Suggested clean-ups from message format V2 review
>
[
https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5026:
Labels: exactly-once tooling (was: )
> DebuggingConsumerId and DebuggingMessageFormatter and messag
[
https://issues.apache.org/jira/browse/KAFKA-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5024:
---
Assignee: Apurva Mehta
> Old clients don't support message format V2
> --
[
https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5021:
Priority: Blocker (was: Major)
> Update Message Delivery Semantics section to take into account KIP
[
https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5020:
Priority: Blocker (was: Major)
> Update protocol documentation to mention message format v2
> -
[
https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5019:
Priority: Blocker (was: Critical)
> Exactly-once upgrade notes
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-4935:
Labels: exactly-once (was: )
> Consider disabling record level CRC checks for message format V2
> -
[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-4935:
Priority: Blocker (was: Major)
> Consider disabling record level CRC checks for message format V2
>
[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-4935:
---
Assignee: Jason Gustafson
> Consider disabling record level CRC checks for message format V2
[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016137#comment-16016137
]
Apurva Mehta commented on KAFKA-4935:
-
The current solution is to provide a light weig
Apurva Mehta created KAFKA-5280:
---
Summary: Protect concurrent access to the cached transaction status
Key: KAFKA-5280
URL: https://issues.apache.org/jira/browse/KAFKA-5280
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5279:
Labels: exactly-once (was: )
> TransactionCoordinator must expire transactionalIds
> --
[
https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5279:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> TransactionCoordinator must expire tra
Apurva Mehta created KAFKA-5279:
---
Summary: TransactionCoordinator must expire transactionalIds
Key: KAFKA-5279
URL: https://issues.apache.org/jira/browse/KAFKA-5279
Project: Kafka
Issue Type: B
[
https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5128:
---
Assignee: Damian Guy
> TransactionCoordinator - Check inter broker protocol and message forma
[
https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5128:
Priority: Blocker (was: Major)
> TransactionCoordinator - Check inter broker protocol and message f
Apurva Mehta created KAFKA-5273:
---
Summary: KafkaConsumer.committed() should get latest committed
offsets from the server
Key: KAFKA-5273
URL: https://issues.apache.org/jira/browse/KAFKA-5273
Project: Ka
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5269:
---
Assignee: Apurva Mehta
> TransactionBounceTest occasionally fails due to partition errors
> -
Apurva Mehta created KAFKA-5270:
---
Summary: TransactionManager should send and `AddOffsetsToTxn`
request only once per group per transaction
Key: KAFKA-5270
URL: https://issues.apache.org/jira/browse/KAFKA-5270
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014864#comment-16014864
]
Apurva Mehta commented on KAFKA-5269:
-
A relevant stack trace:
{noformat}
[2017-05-17
[
https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5269:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> TransactionBounceTest occasionally fai
Apurva Mehta created KAFKA-5269:
---
Summary: TransactionBounceTest occasionally fails due to partition
errors
Key: KAFKA-5269
URL: https://issues.apache.org/jira/browse/KAFKA-5269
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5268:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> TransactionsBounceTest occasionally se
Apurva Mehta created KAFKA-5268:
---
Summary: TransactionsBounceTest occasionally sees
INVALID_TXN_STATE errors
Key: KAFKA-5268
URL: https://issues.apache.org/jira/browse/KAFKA-5268
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5247:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> Consumer GroupCoordinator should conti
[
https://issues.apache.org/jira/browse/KAFKA-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5231:
Issue Type: Sub-task (was: Bug)
Parent: KAFKA-4815
> TransactinoCoordinator does not bump e
[
https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010959#comment-16010959
]
Apurva Mehta commented on KAFKA-5247:
-
Note that this is only an issue when we mix off
Apurva Mehta created KAFKA-5247:
---
Summary: Consumer GroupCoordinator should continue to materialize
committed offsets in offset order even for transactional offset commits
Key: KAFKA-5247
URL: https://issues.apache.
Apurva Mehta created KAFKA-5231:
---
Summary: TransactinoCoordinator does not bump epoch when aborting
open transactions
Key: KAFKA-5231
URL: https://issues.apache.org/jira/browse/KAFKA-5231
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005584#comment-16005584
]
Apurva Mehta commented on KAFKA-5213:
-
This also explains why it wasn't seen till now:
[
https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005575#comment-16005575
]
Apurva Mehta commented on KAFKA-5213:
-
The fix is to mark the builder as `full` if the
[
https://issues.apache.org/jira/browse/KAFKA-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005570#comment-16005570
]
Apurva Mehta commented on KAFKA-5213:
-
I found the bug. The problem is that in a parti
Apurva Mehta created KAFKA-5160:
---
Summary: KIP-98 : broker side handling for the
TxnOffsetCommitRequest
Key: KAFKA-5160
URL: https://issues.apache.org/jira/browse/KAFKA-5160
Project: Kafka
Iss
Apurva Mehta created KAFKA-5147:
---
Summary: KafkaProducer's TransactionManager needs a review on
synchronization
Key: KAFKA-5147
URL: https://issues.apache.org/jira/browse/KAFKA-5147
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987228#comment-15987228
]
Apurva Mehta commented on KAFKA-4477:
-
Your stack trace alone doesn't indicate that yo
Apurva Mehta created KAFKA-5126:
---
Summary: Implement KIP-98 transactional methods in the MockProducer
Key: KAFKA-5126
URL: https://issues.apache.org/jira/browse/KAFKA-5126
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983276#comment-15983276
]
Apurva Mehta commented on KAFKA-4970:
-
This is different. This is to make the 'produc
Apurva Mehta created KAFKA-5080:
---
Summary: Convert ProducerBounceTest to use the new KafkaConsumer
Key: KAFKA-5080
URL: https://issues.apache.org/jira/browse/KAFKA-5080
Project: Kafka
Issue Typ
Apurva Mehta created KAFKA-5079:
---
Summary: ProducerBounceTest fails occasionally with a
SocetTimeoutException
Key: KAFKA-5079
URL: https://issues.apache.org/jira/browse/KAFKA-5079
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-5079:
Summary: ProducerBounceTest fails occasionally with a
SocketTimeoutException (was: ProducerBounceTe
Apurva Mehta created KAFKA-5062:
---
Summary: Kafka brokers can accept malformed requests which
allocate gigabytes of memory
Key: KAFKA-5062
URL: https://issues.apache.org/jira/browse/KAFKA-5062
Project: K
[
https://issues.apache.org/jira/browse/KAFKA-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-4818:
Description: This covers the implementation of the producer and consumer to
support transactions.
[
https://issues.apache.org/jira/browse/KAFKA-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-4818:
Description: This covers the implementation of the producer and consumer to
support transactions, as
[
https://issues.apache.org/jira/browse/KAFKA-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-4818:
---
Assignee: Apurva Mehta (was: Guozhang Wang)
> Implement transactional producer
> ---
Apurva Mehta created KAFKA-5053:
---
Summary: Send Error messages along with FindCoordinatorResponse
Key: KAFKA-5053
URL: https://issues.apache.org/jira/browse/KAFKA-5053
Project: Kafka
Issue Type
Apurva Mehta created KAFKA-5052:
---
Summary: We shouldn't pass the underlying exception to
RetriableCommitFailedException when an async offset commit fails.
Key: KAFKA-5052
URL: https://issues.apache.org/jira/browse/K
Apurva Mehta created KAFKA-5043:
---
Summary: Add FindCoordinatorRequest RPC stub and update
InitPidRequest for KIP-98
Key: KAFKA-5043
URL: https://issues.apache.org/jira/browse/KAFKA-5043
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta reassigned KAFKA-5033:
---
Assignee: Apurva Mehta
> Reconsider default retries for idempotent producer
> ---
Apurva Mehta created KAFKA-4976:
---
Summary: DumpLogSegments should print the contents of the pid
snapshot files
Key: KAFKA-4976
URL: https://issues.apache.org/jira/browse/KAFKA-4976
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-4970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946333#comment-15946333
]
Apurva Mehta commented on KAFKA-4970:
-
cc [~junrao] [~hachikuji] -- this is based on o
Apurva Mehta created KAFKA-4970:
---
Summary: Add a 'ProducerIdResource' to enable authorization for
generating producer ids
Key: KAFKA-4970
URL: https://issues.apache.org/jira/browse/KAFKA-4970
Project: K
[
https://issues.apache.org/jira/browse/KAFKA-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941193#comment-15941193
]
Apurva Mehta commented on KAFKA-4817:
-
There is some subtlety in the idempotent produc
[
https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Apurva Mehta updated KAFKA-4935:
Issue Type: Improvement (was: Bug)
> Disable record level crc checks on the consumer with the KIP-9
Apurva Mehta created KAFKA-4935:
---
Summary: Disable record level crc checks on the consumer with the
KIP-98 message format
Key: KAFKA-4935
URL: https://issues.apache.org/jira/browse/KAFKA-4935
Project: K
[
https://issues.apache.org/jira/browse/KAFKA-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15935601#comment-15935601
]
Apurva Mehta commented on KAFKA-4816:
-
I compiled the perf numbers for this patch, res
[
https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905989#comment-15905989
]
Apurva Mehta commented on KAFKA-4574:
-
I posted all the information I could glean from
[
https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905983#comment-15905983
]
Apurva Mehta commented on KAFKA-4574:
-
Here is everything from the state change logs.
[
https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905939#comment-15905939
]
Apurva Mehta commented on KAFKA-4574:
-
Here are all the leader changes for this partit
[
https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905837#comment-15905837
]
Apurva Mehta commented on KAFKA-4574:
-
>From the server logs, we see that the logs wer
[
https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905778#comment-15905778
]
Apurva Mehta commented on KAFKA-4574:
-
It appears than different messages wound up at
201 - 300 of 340 matches
Mail list logo
