GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4146
MINOR: Tighten up locking when aborting expired transactions
This is a followup to #4137
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4137
KAFKA-6119: Bump epoch when expiring transactions in the
TransactionCoordinator
A description of the problem is in the JIRA. I have added an integration
test which reproduces the original scenario
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4057
KAFKA-6053: Fix NoSuchMethodError when creating ProducerRecords with older
client versions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user apurvam closed the pull request at:
https://github.com/apache/kafka/pull/2677
---
Github user apurvam closed the pull request at:
https://github.com/apache/kafka/pull/3266
---
Github user apurvam closed the pull request at:
https://github.com/apache/kafka/pull/4020
---
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4039
MINOR: Bump the request timeout for the transactional message copier
Multiple inflights means that when there are rolling bounces and other
cluster instability, there is an
increased likelihood
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4029
KAFKA-6016: Make the reassign partitions system test use the idempotent
producer
With these changes, we are ensuring that the partitions being reassigned
are from non-zero offsets. We also ensure
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4022
KAFKA-6015: Fix NullPointerExceptionInRecordAccumulator
It is possible for batches with sequence numbers to be in the `deque` while
at the same time the in flight batches in the `TransactionManager
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4020
KAFKA-6003: Accept appends on replicas and when rebuilding the log
unconditionally
This is a port of #4004 for the 0.11.0 branch.
With this patch so that we _only_ validate appends which
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/4004
KAFKA-6003: Accept appends on replicas unconditionally when local producer
state doesn't exist
Without this patch, if the replica's log was somehow truncated before
the leader's
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3969
KAFKA-5888: System test to check ordering of messages with transactions and
max.in.flight > 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3947
KAFKA-5959: Fix NPE in Sender.canRetry when idempotence is not enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka KAFKA-5959
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3896
KAFKA-5914 add message format version and message max bytes to metadata
response
Updated the `TopicResponse` part of the `MetadataResponse` to include the
message format version and the message
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3878
KAFKA-5913: Add the RecordMetadataNotAvailableException
We return this exception from `RecordMetadata.offset()` or
`RecordMetadata.timestamp()` if these pieces of metadata were not returned by
the
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3877
MINOR: Disable KafkaAdminClientTest.testHandleTimeout
This test is super flaky in the PR builder.
https://issues.apache.org/jira/browse/KAFKA-5792 tracks the fix.
You can merge this pull request
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3865
KAFKA-5793: Tighten up the semantics of the OutOfOrderSequenceException
*WIP : Don't review yet, still to add tests*
Description of the solution can be found here:
https://cwiki.apach
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3743
KAFKA-5494: enable idempotence with max.in.flight.requests.per.connection >
1
Here we introduce client and broker changes to support multiple inflight
requests while still guaranteeing idempote
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3550
KAFKA-5610: KafkaApis.HandleWriteTxnMarkerRequest should return
UNKNOWN_TOPIC_OR_PARTITION on partition emigration.
Before this patch, we would return the non-retriable
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3462
KAFKA-5543: Remove all partition metrics when a topic is deleted
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
KAFKA-5543
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3441
MINOR: Enable the TransactionsBounceTest
I'll let this have multiple runs on the branch builder to see if it fails,
and investigate if so.
You can merge this pull request into a Git reposito
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3400
Enable transactions in ProducerPerformance Tool
With this patch, the `ProducePerfomance` tool can create transactions of
differing durations.
This patch was used to to collect the initial
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3377
KAFKA-5477: Lower retryBackoff for AddPartitionsRequest
This patch lowers the retry backoff when receiving a
CONCURRENT_TRANSACTIONS error from an AddPartitions request. The default of
100ms would
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3374
KAFKA-5032: Update the docs for message size configs across the board
Before 0.11, we used to have limits for maximum message size on the
producer, broker, and consumer side.
From 0.11
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3360
KAFKA-5020: Update message format in implementation docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
KAFKA-5020-message
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3355
KAFKA-5457: MemoryRecordsBuilder.hasRoomFor should account for record
headers
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3353
KAFKA-5455 - Better Javadocs for the transactional producer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
KAFKA-5455-proper
Github user apurvam closed the pull request at:
https://github.com/apache/kafka/pull/3346
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3346
MINOR: Cleanups for TransactionsTest
The motivation is that KAFKA-5449 seems to indicate that producer instances
can be shared across tests, and that producers from one test seem to be hitting
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3343
WIP: KAFKA-5449: fix bad state transition in transaction manager
The
`kafka.api.TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData`
very rarely sees the following.
I
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3313
KAFKA-5438: Fix UnsupportedOperationException in writeTxnMarkersRequest
Before this patch, the `partitionErrors` was an immutable map. As a result
if a single producer had a marker for multiple
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3308
KAFKA-5437: Always send a sig_kill when cleaning the message copier
When the message copier hangs (like when there is a bug in the client), it
ignores the sigterm and doesn't shut down. this l
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3286
KAFKA-5415: Remove timestamp check in completeTransitionTo
This assertion is hard to get right because the system time can roll
backward on a host due to NTP (as shown in the ticket), and also
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3285
KAFKA-5422: Handle multiple transitions to ABORTABLE_ERROR correctly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
KAFKA-5422
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3278
WIP: MINOR: Add logging and a small bug fix for the transaction coordinator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3266
KAFKA-5403: Transaction system test consumer should dedup messages by offset
Since the consumer can consume duplicate offsets due to rebalances, we
should dedup consumed messages by offset in order
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3261
MINOR: Set log level for producer internals to trace for transactions test
We need to debug most issues with the transactions system test.
You can merge this pull request into a Git repository by
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3252
KAFKA-5385: ProducerBatch expiry should go through Sender.failBatch
Before this patch, we would call `producerBatch.done` directly from the
accumulator when expiring batches. This meant that we
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3218
KAFKA-5373 : Revert breaking change to console consumer
This patch b63e41ea78a58bdea78be33f90bfcb61ce5988d3 since it broke the
console consumer -- the consumer prints the addresses of the messages
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3217
KAFKA-5366: Add concurrent reads to transactions system test
This currently fails in multiple ways. One of which is most likely
KAFKA-5355, where the concurrent consumer reads duplicates
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3216
HOTFIX: Reinstate the placeholder for logPrefix in TransactionManager
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
HOTFIX
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3204
KAFKA-5322: Add an `OPERATION_NOT_ATTEMPTED` error code
In the `AddPartitionsToTxn` request handling, if even one partition fails
authorization checks, the entire request is essentially failed
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3202
KAFKA-5364: Don't fail producer if drained partition is not yet in
transaction
Due to the async nature of the producer, it is possible to attempt to drain
a messages whose partition hasn&#
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3184
KAFKA-5351: Reset pending state when returning an error in
appendTransactionToLog
Without this patch, future client retries would get the
`CONCURRENT_TRANSACTIONS` error code indefinitely, since
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3149
KAFKA-5281: System tests for transactions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
KAFKA-5281-transactions-system-tests
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3132
KAFKA-5147: Add missing synchronization to TransactionManager
The basic idea is that exactly three collections, ie. `pendingRequests`,
`newPartitionsToBeAddedToTransaction`, and
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3119
KAFKA-5273: Make KafkaConsumer.committed query the server for all partitions
Before this patch the consumer would return the cached offsets for
partitions in its current assignment. This worked
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3108
KAFKA-5247: Materialize committed offsets in offset order
With this patch, offset commits are always materialized according to the
order of the commit records in the offsets topic.
Before
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3094
KAFKA-5269: Correct handling of UNKNOWN_TOPIC_OR_PARTITION error
We should retry AddPartitionsToTxnRequest and TxnOffsetCommitRequest when
receiving an UNKNOWN_TOPIC_OR_PARTITION error
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3093
HOTFIX: Close transactional producers in all new tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
HOTFIX-close-leaked
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3091
KAFKA-5033: Set default retries for the idempotent producer to be infinite.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/3015
KAFKA-5213; Mark a MemoryRecordsBuilder as full as soon as the append
stream is closed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2994
KAFKA-5188: Integration tests for transactions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
KAFKA-5188-exactly-once
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2970
Kafka-5160; KIP-98 Broker side support for TxnOffsetCommitRequest
This patch adds support for the `TxnOffsetCommitRequest` added in KIP-98.
Desired handling for this request is [described
here
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2961
MINOR: Serialize the real isolationLevel in FetchRequest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
MINOR-serialize
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2840
KAFKA-4818: Exactly once transactional clients
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apurvam/kafka
exactly-once-transactional
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2825
KAFKA-5043 : Add FindCoordinatorRPC stub and update InitPidRequest for
transactions in KIP-98.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2809
CPKAFKA-465 : Exactly once transactional producer -- initial implementation
The basic flow works: find coordinator, get pid, add partitions to
transaction, commit/abort.
Still to add
Github user apurvam closed the pull request at:
https://github.com/apache/kafka/pull/2809
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2796
Close the producer batch data stream when the batch gets full to free up
compression buffers, etc.
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2735
KAFKA-4815 : Add idempotent producer semantics
This is from the KIP-98 proposal.
The main points of discussion surround the correctness logic, particularly
the Log class where incoming
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2677
MINOR: set trace logging for zookeeper upgrade test
This adds logging which will hopefully help root cause
https://issues.apache.org/jira/browse/KAFKA-4574.
You can merge this pull request into a
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2567
MINOR: Increase consumer init timeout in throttling test
The throttling system test sometimes fail because it takes longer than the
current 10 second time out for partitions to get assigned to the
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2347
Initial commit of partition assignment check in console consumer.
With this patch, the consumer will considered initialized in the
ProduceConsumeValidate tests only if it has partitions assigned
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2278
KAFKA-4526 - Disable throttling test until it can be fixed correctly.
At present, the test is fragile in the sense that the console consumer
has to start and be initialized before the verifiable
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/2089
Fix documentation of compaction
Also cleaned up some of the language around compaction guarantees.
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/1910
KAFKA-4214:kafka-reassign-partitions fails all the time when brokers are
bounced during reassignment
There is a corner case bug, where during partition reassignment, if the
controller and a
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/1904
KAFKA-4213: First set of system tests for replication throttling, KIP-73.
This patch also fixes the following:
1. KafkaService.verify_reassign_partitions did not check whether
Github user apurvam closed the pull request at:
https://github.com/apache/kafka/pull/1903
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user apurvam opened a pull request:
https://github.com/apache/kafka/pull/1903
KAFKA-4213: First set of system tests for replication throttling
Added the first set of system tests for replication quotas. These tests
validate throttling behavior during partition reassigment
70 matches
Mail list logo
