zhang shuai created KAFKA-4119:
--
Summary: Get topic offset with Kafka SSL&ACL
Key: KAFKA-4119
URL: https://issues.apache.org/jira/browse/KAFKA-4119
Project: Kafka
Issue Type: Bug
Compo
Hi Dong,
If you set the cluster.id in the config, the problem is how you
change/update the cluster.id .
You will need to change the all the config files and make sure every one of
them is correct as well as update the ZK metadata. This will require a
reboot/downtime of the entire cluster, wherea
[
https://issues.apache.org/jira/browse/KAFKA-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhang shuai updated KAFKA-4119:
---
Description:
I have a kafka cluster with SSL&ACL when i trun off ACL,i can get offset form
kafka-cons
Thanks for the KIP, Ismael, looks great. I have just a couple of comments and
questions:
- I assume the znode containing the cluster id is persistent. Is there ever the
need to delete that znode to force a new instance id, and if so, how is it
expected to happen? I'm thinking about a scenario i
Hey Sumit,
Thanks Sumit for your explanation. It seems that the concern is that we can
not easily change cluster.id if we read this from config. Maybe the KIP
should also specify the requirement for users to change the cluster.id.
But it seems to me that it is equally straightforward to change cl
Hi Flavio,
I have added some comments inline based on my understanding of the
implementation but Ismael probably can add more to this from an
architectural perspective.
Cheers,
Sumit
On Sat, Sep 3, 2016 at 8:48 AM, Flavio Junqueira wrote:
> Thanks for the KIP, Ismael, looks great. I have just
Hi Dong,
Please see my comments inline.
Sumit
On Sat, Sep 3, 2016 at 9:26 AM, Dong Lin wrote:
> Hey Sumit,
>
> Thanks Sumit for your explanation. It seems that the concern is that we can
> not easily change cluster.id if we read this from config. Maybe the KIP
> should also specify the require
Greg Fodor created KAFKA-4120:
-
Summary: byte[] keys in RocksDB state stores do not work as
expected
Key: KAFKA-4120
URL: https://issues.apache.org/jira/browse/KAFKA-4120
Project: Kafka
Issue Ty
This vote is now closed. KIP-77 is accepted with
+3 (binding)
+5 (non-binding)
Thanks for voting and feedback!
-Matthias
On 08/31/2016 06:16 PM, Jim Jagielski wrote:
> +1
>
>> On Aug 29, 2016, at 5:50 AM, Matthias J. Sax wrote:
>>
>> I’d like to initiate the voting process for KIP-77:
>>
>>
Joaquin Casares created KAFKA-4121:
--
Summary: Allow creating broker listeners from hostname
Key: KAFKA-4121
URL: https://issues.apache.org/jira/browse/KAFKA-4121
Project: Kafka
Issue Type: I
[
https://issues.apache.org/jira/browse/KAFKA-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joaquin Casares updated KAFKA-4121:
---
Description:
I'm attempting to start a docker container using the parameter:
{CODE}
advertise
Hi Sumit,
Please see my comments inline.
On Sat, Sep 3, 2016 at 10:33 AM, sumit arrawatia
wrote:
> Hi Dong,
>
> Please see my comments inline.
>
> Sumit
>
> On Sat, Sep 3, 2016 at 9:26 AM, Dong Lin wrote:
>
> > Hey Sumit,
> >
> > Thanks Sumit for your explanation. It seems that the concern is
Hi Dong,
Please find my comments inline.
Hopefully they address your concerns.
Have a great weekend !
Sumit
On Sat, Sep 3, 2016 at 3:17 PM, Dong Lin wrote:
> Hi Sumit,
>
> Please see my comments inline.
>
> On Sat, Sep 3, 2016 at 10:33 AM, sumit arrawatia <
> sumit.arrawa...@gmail.com>
> wrot
Shane Hender created KAFKA-4122:
---
Summary: Consumer startup swallows DNS resolution exception and
infinitely retries
Key: KAFKA-4122
URL: https://issues.apache.org/jira/browse/KAFKA-4122
Project: Kafka
Hey Sumit,
I have no doubt that there are benefits with using tags. But the usage of
tags is actually orthogonal to the usage of cluster.id. I am not sure the
benefits of using tags that you provided can help us decide whether
randomly generated cluster.id is better than readable cluster.id from
c
15 matches
Mail list logo
