[jira] [Created] (KAFKA-7880) KafkaConnect should standardize worker thread name

YeLiang created KAFKA-7880: -- Summary: KafkaConnect should standardize worker thread name Key: KAFKA-7880 URL: https://issues.apache.org/jira/browse/KAFKA-7880 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-7879) Data directory size decreases every few minutes when producer is sending large amount of data

Pradeep Bansal created KAFKA-7879: - Summary: Data directory size decreases every few minutes when producer is sending large amount of data Key: KAFKA-7879 URL: https://issues.apache.org/jira/browse/KAFKA-7879

[jira] [Resolved] (KAFKA-7876) Broker suddenly got disconnected

[ https://issues.apache.org/jira/browse/KAFKA-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Lazam resolved KAFKA-7876. -- Resolution: Duplicate > Broker suddenly got disconnected > -

Re: [VOTE] KIP-258: Allow to Store Record Timestamps in RocksDB

Hi, during PR reviews, we discovered a couple of opportunities to simply and improve the KIP and code. Thus, the following minor changes to the public API are done (the KIP is already updated). I revote is not necessary as the changes are minor. - interface `ValueAndTimestamp` is going to be a

[VOTE] KIP-417: Allow JmxTool to connect to a secured RMI port

Hi, All: I would like to start a vote on KIP-417 which aims at supporting JmxTool to connect to a secured RMI port. The KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-417%3A+Allow+JmxTool+to+connect+to+a+secured+RMI+port Thanks! Fangbin

kafka stream depends on it's own derived table

hi, I was writing a simple stream app, all it does is producer send a sequence of path and value, for example path /0 , value 1 path /0/1, value 2 path /0/1/2, value 3 and kafka stream take those input and produce a ktable store. There is a rule. if parent path is not exist, then child can not

Re: [DISCUSS] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

Hi Ismael, thanks for bringing up serialization in the discussion! Indeed, JSON was considered given it's the prevalent text-based serialization option. In comparison to flatbuffers, most generic pros and cons are valid in this context too. Higher perfomance during serde, small size, optional

[jira] [Created] (KAFKA-7878) Connect Task already exists in this worker when failed to create consumer

Loïc Monney created KAFKA-7878: -- Summary: Connect Task already exists in this worker when failed to create consumer Key: KAFKA-7878 URL: https://issues.apache.org/jira/browse/KAFKA-7878 Project: Kafka

Kafka Version Detection for Rolling Upgrade

Hello, I am struggling a little bit to do the rolling upgrade. My confusion is mainly where the version numbers should be. I am verifying my steps using main site guidelines. Any help would be appreciated https://kafka.apache.org/documentation/#ecosystem I am upgrading from *2.11-1.1.0* to

Re: [DISCUSS] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

Jason, Ewen, great discussion w.r.t. the proposed config. I agree that making 'compatible' the new default is a nice suggestion and makes sense. The cost in metadata is acceptable. However, while I also like being as conservative as possible in suggesting addition of new configs, I feel that this

RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer

So... Does this non-response mean I should drop this topic after almost one month, folks? -Original Message- From: ChienHsing Wu Sent: Monday, January 21, 2019 12:47 PM To: dev@kafka.apache.org Subject: RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions

[jira] [Created] (KAFKA-7877) Connect DLQ not used in SinkTask put()

Andrew Bourgeois created KAFKA-7877: --- Summary: Connect DLQ not used in SinkTask put() Key: KAFKA-7877 URL: https://issues.apache.org/jira/browse/KAFKA-7877 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-183 - Change PreferredReplicaLeaderElectionCommand to use AdminClient

Hi Folks, It took a while, but the work for KIP-183 has now been merged. My thanks to everyone involved. A few details changed between what was voted on and what ultimately got merged. I've updated the KIP to reflect what was actually merged. If anyone is interested in the gory details they can

Some jira cleanup

All, I left a few comments on some old but still open jiras in an attempt to clean up a little bit. Since probably no one would notice these comments I thought I'd quickly list them here to give people a chance to check on them: KAFKA-217 :