Build failed in Jenkins: kafka-2.0-jdk8 #83

See Changes: [jason] KAFKA-6897; Prevent KafkaProducer.send from blocking when producer is -- [...truncated 2.48 MB...]

Jenkins build is back to normal : kafka-trunk-jdk10 #306

See

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Hmm, since we already use controller epoch and leader epoch for properly caching the latest partition state, do we really need correlation id for ordering the controller requests? Thanks, Jun On Fri, Jul 20, 2018 at 2:18 PM, Becket Qin wrote: > Lucas and Mayuresh, > > Good idea. The

Re: Kafka topic retention question

Ah, common source of confusion! Each partition is divided into 1GB segments. And the active segment, the one you are currently writing into, is never deleted. So, until you write 1GB, you will see all messages. If you need more accurate retention, you can configure smaller segment size for low

[jira] [Resolved] (KAFKA-7152) replica should be in-sync if its LEO equals leader's LEO

[ https://issues.apache.org/jira/browse/KAFKA-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7152. - Resolution: Fixed > replica should be in-sync if its LEO equals leader's LEO >

Re: [DISCUSS] KIP-342 Add Customizable SASL extensions to OAuthBearer authentication

Hi Stanislav and Rajini. If SaslExtensions is going to part of the public API, then it occurred to me that one of the requirements of all SASL extensions is that the keys and values need to match mechanism-specific regular expressions. For example, RFC 5802 ( https://tools.ietf.org/html/rfc5802)

Kafka topic retention question

I have been diving into to Kafka for the last couple of weeks. I am running some low volume (5-10 TPS) production data. I had set a default retention period on all the topics for 48 hours. I have just noticed there is some behavior I don't understand. I see messages in the topic that are over a

Jenkins build is back to normal : kafka-trunk-jdk8 #2818

See

Build failed in Jenkins: kafka-2.0-jdk8 #81

See Changes: [ismael] MINOR: Change "no such session ID" log to debug (#5316) -- [...truncated 2.48 MB...] org.apache.kafka.streams.TopologyTest >

Build failed in Jenkins: kafka-trunk-jdk10 #304

See Changes: [ismael] MINOR: Fix logged timeout in KafkaProducer.close() (#4623) [ismael] MINOR: Change "no such session ID" log to debug (#5316) -- [...truncated 1.54

Build failed in Jenkins: kafka-trunk-jdk8 #2817

See Changes: [lindong28] KAFKA-7177; Update 2.0 documentation to reflect changed quota behaviors -- [...truncated 884.80 KB...] kafka.utils.SchedulerTest >

[jira] [Resolved] (KAFKA-7154) Apache kafka getting shut down everytime it is started

[ https://issues.apache.org/jira/browse/KAFKA-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7154. -- Resolution: Information Provided > Apache kafka getting shut down everytime it is started >

Build failed in Jenkins: kafka-trunk-jdk8 #2816

See Changes: [ismael] MINOR: FileStreamSinkTask should create file if it doesn't exist (#5406) -- [...truncated 888.89 KB...] kafka.admin.TopicCommandTest >

[jira] [Resolved] (KAFKA-7177) Update 2.0 documentation to reflect changed quota behaviors by KIP-219

[ https://issues.apache.org/jira/browse/KAFKA-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-7177. - Resolution: Fixed > Update 2.0 documentation to reflect changed quota behaviors by KIP-219 >

[jira] [Resolved] (KAFKA-2008) Update num.consumer.fetchers description in Kafka documentation

[ https://issues.apache.org/jira/browse/KAFKA-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2008. -- Resolution: Auto Closed Closing issue related old consumer configs. Old consumer config doc section

[jira] [Resolved] (KAFKA-1970) Several tests are not stable

[ https://issues.apache.org/jira/browse/KAFKA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1970. -- Resolution: Auto Closed Closing inactive issue > Several tests are not stable >

Re: [DISCUSS] KIP-263: Allow broker to skip sanity check of inactive segments on broker startup

Here is some information related to the KIP. Previously we thought we can ignore the sanity check by default to speedup broker startup and there is no need for extra configuration. However based on the code and some previous experiment result it is not clear whether it will work. When

Re: [VOTE] KIP-322: Return new error code for DeleteTopics API when topic deletion disabled.

*Hi All,The vote has passed with 3 binding votes (Gwen, Harsha, Jason) and 8 non-binding votes (Vahid, Mickael, Ted, Daniele, Satish, Magnus, Kamal, Eno).Thanks everyone for the votes.Thanks,Manikumar* On Sat, Jul 21, 2018 at 12:26 AM Jason Gustafson wrote: > Thanks, +1 from me. > > On Fri,

Re: [VOTE] KIP-340: Allow kafka-reassign-partitions.sh and kafka-log-dirs.sh to take admin client property file

Thanks to everyone who voted and provided feedback! This KIP is now adopted with 3 binding +1s (Jason, Joel, Dong) and 1 non-binding +1 (Ted). Regards, Dong On Fri, Jul 20, 2018 at 11:20 PM, Joel Koshy wrote: > +1 > > On Tue, Jul 17, 2018 at 1:42 PM, Ted Yu wrote: > > > +1 > > > > On Tue,

Re: [VOTE] KIP-340: Allow kafka-reassign-partitions.sh and kafka-log-dirs.sh to take admin client property file

+1 On Tue, Jul 17, 2018 at 1:42 PM, Ted Yu wrote: > +1 > > On Tue, Jul 17, 2018 at 1:40 PM Jason Gustafson > wrote: > > > +1. This is useful (though the naming inconsistencies in the tools are > > vexing, as always). > > > > -Jason > > > > On Tue, Jul 17, 2018 at 12:24 PM, Dong Lin wrote: > >