Hello there,
I just signed the petition "Facebook: Save Wilpattu One Srilanka's Most
Loved Place" and wanted to see if you could help by adding your name.
Our goal is to reach 7,500 signatures and we need more support. You can
read more and sign the petition here:
http://chng.it/ZxfxKQcqqk
Than
Matthias J. Sax created KAFKA-8141:
--
Summary: Flaky Test
FetchRequestDownConversionConfigTest#testV1FetchWithDownConversionDisabled
Key: KAFKA-8141
URL: https://issues.apache.org/jira/browse/KAFKA-8141
Matthias J. Sax created KAFKA-8140:
--
Summary: Flaky Test
SaslSslAdminClientIntegrationTest#testDescribeAndAlterConfigs
Key: KAFKA-8140
URL: https://issues.apache.org/jira/browse/KAFKA-8140
Project: K
Matthias J. Sax created KAFKA-8139:
--
Summary: Flaky Test
SaslSslAdminClientIntegrationTest#testMetadataRefresh
Key: KAFKA-8139
URL: https://issues.apache.org/jira/browse/KAFKA-8139
Project: Kafka
Matthias J. Sax created KAFKA-8138:
--
Summary: Flaky Test
PlaintextConsumerTest#testFetchRecordLargerThanFetchMaxBytes
Key: KAFKA-8138
URL: https://issues.apache.org/jira/browse/KAFKA-8138
Project: Ka
Matthias J. Sax created KAFKA-8137:
--
Summary: Flaky Test
LegacyAdminClientTest#testOffsetsForTimesWhenOffsetNotFound
Key: KAFKA-8137
URL: https://issues.apache.org/jira/browse/KAFKA-8137
Project: Kaf
Hi,
We have a Kafka cluster (version 1.1.1) where one node unexpectedly failed.
After that consumers from a couple of consumers are stuck in the poll() API
call. Looking at the thread dump, it looks like the consumer is stuck in
org.apache.kafka.clients.consumer.internals.AbstractCoordinator.
Matthias J. Sax created KAFKA-8136:
--
Summary: Flaky Test MetadataRequestTest#testAllTopicsRequest
Key: KAFKA-8136
URL: https://issues.apache.org/jira/browse/KAFKA-8136
Project: Kafka
Issue T
Hello Boyang,
I've made another thorough pass over this KIP and I'd like to spilt it into
two parts: the first part, covered in KIP-429 would be touching on Consumer
Coordinator only to have incremental rebalance protocol in place. The
second part (for now I've reserved KIP number 444 for it) woul
Thanks Ryanne. These were good questions.
-Jason
On Wed, Mar 20, 2019 at 5:19 PM Ryanne Dolan wrote:
> Thanks Jason, that helps. I agree my concerns are orthogonal to reducing
> cross-DC transfer costs -- I'm only interested in how this affects what
> happens when a rack is unavailable, since,
Hi George,
One big problem here is that administrative APIs should be done through RPCs,
not through ZooKeeper. KIP-4 (Command line and centralized administrative
operations) describes the rationale for this. We want public and stable APIs
that don't depend on the internal representation of s
Thanks Jason, that helps. I agree my concerns are orthogonal to reducing
cross-DC transfer costs -- I'm only interested in how this affects what
happens when a rack is unavailable, since, as the name implies, the whole
point of stretching a cluster across availability zones is for increased
availab
Hi Ryanne,
Thanks, responses below:
Thanks Jason, I see that the proposed ReplicaSelector would be where that
> decision is made. But I'm not certain how a consumer triggers this process?
> If a consumer can't reach its preferred rack, how does it ask for a new
> assignment?
As documented in th
Guozhang Wang created KAFKA-8135:
Summary: Kafka Producer deadlocked on flush call with intermittent
broker unavailability
Key: KAFKA-8135
URL: https://issues.apache.org/jira/browse/KAFKA-8135
Project
Sam Lendle created KAFKA-8134:
-
Summary: ProducerConfig.LINGER_MS_CONFIG undocumented breaking
change in kafka-clients 2.1
Key: KAFKA-8134
URL: https://issues.apache.org/jira/browse/KAFKA-8134
Project: Ka
+1 (binding)
Verified quick start using kafka_2.11 and kafka_2.12 binaries. Built from
source and ran tests. Checked release notes, javadoc and documentation.
Thanks for running the release, Matthias!
Regards,
Rajini
On Wed, Mar 20, 2019 at 7:30 PM Bill Bejeck wrote:
> +1 (non-binding)
>
>
Hi Noa,
My understanding was the KIP-398 is proposing to look up only SSL
truststores from CLASSPATH, not files that contain actual credentials like
SSL keystores. In production scenarios, lots of users tend to use
certificates signed by trusted CAs, so you don't actually need to configure
a trust
Hi Noa,
I think Jun makes a good point that this would be better as a generic
mechanism, not specific to SSL. With KIP-421: Support resolving externalized
secrets in AbstractConfig, we should be able to do something like that. We
could have a ClasspathConfigProvider. Then this could be used
+1 (non-binding)
- Validated signature
- build from source and ran tests (all passed)
- verified the quick start and Kafka Streams quick start
On Sat, Mar 9, 2019 at 5:56 PM Matthias J. Sax
wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the third candidate for release
Thanks Jason, I see that the proposed ReplicaSelector would be where that
decision is made. But I'm not certain how a consumer triggers this process?
If a consumer can't reach its preferred rack, how does it ask for a new
assignment?
I suppose a consumer that can't reach its preferred rack would n
Matthias J. Sax created KAFKA-8133:
--
Summary: Flaky Test MetadataRequestTest#testNoTopicsRequest
Key: KAFKA-8133
URL: https://issues.apache.org/jira/browse/KAFKA-8133
Project: Kafka
Issue Ty
Matthias J. Sax created KAFKA-8132:
--
Summary: Flaky Test MirrorMakerIntegrationTest
#testCommaSeparatedRegex
Key: KAFKA-8132
URL: https://issues.apache.org/jira/browse/KAFKA-8132
Project: Kafka
3 broker with replication factor 2 ? Isn't that already problematic?
Have you considered extending the partition as 3 (since you have 3
brokers), and give a try? Can you afford extension to 1 more broker?
On Wed, 20 Mar 2019 at 16:02, Barguje, Bharat, Vodafone Group <
bharat.barg...@vodafone.com>
Hi Team,
I am using Apache Kafka stateful set, I have setup like 3 Zookeeper, 3 Kafka
broker, Replication factor is 2.
I have 2 microservices with 2 kafka consumers, Kafka topic has 2 partition, I
could see 1 consumer is dead as per the command to display consumer group, But
it still processin
[
https://issues.apache.org/jira/browse/KAFKA-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
laomei resolved KAFKA-7723.
---
Resolution: Duplicate
> Kafka Connect support override worker kafka api configuration with connector
> confi
[
https://issues.apache.org/jira/browse/KAFKA-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7978.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-8098. Feel free to reopen the issue, If occurs
a
[
https://issues.apache.org/jira/browse/KAFKA-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-8098.
--
Resolution: Fixed
Fix Version/s: 2.2.1
> Flaky Test AdminClientIntegrationTest#testConsumerGroup
Hey there everybody,
Thank you Dongjin for summarizing the vote results.
I've updated the KIP with a link to the voting thread and the state of
accepted.
I also wanted to let everybody know that we have an open PR that is ready
for review - https://github.com/apache/kafka/pull/6318
Thanks,
Stani
Hi all
Kafka-1194 has been a longstanding issue and now there seems to be a viable
fix that also passes tests. I know Windows isn't a priority, but as I
mentioned before, avoiding a fatal un-recoverable crash for newcomers
learning Kafka is very important.
I don't have enough core Kafka expertise
Sönke Liebau created KAFKA-8131:
---
Summary: Add --version parameter to command line help outputs &
docs
Key: KAFKA-8131
URL: https://issues.apache.org/jira/browse/KAFKA-8131
Project: Kafka
Issu
ouyangwulin created KAFKA-8130:
--
Summary: The consumer is not closed in GetOffsetShell, will
exhausted socket channel when frequent calls
Key: KAFKA-8130
URL: https://issues.apache.org/jira/browse/KAFKA-8130
31 matches
Mail list logo
