I'll keep an eye on that and other topics in all my four environments to
see when it appears again For the moment it's fine
On 02-Oct-19 7:50 AM, M. Manna wrote:
I don’t think you can control replication using clients (pub/sub). And
neither should you be allowed to.
I guess we need more o
I don’t think you can control replication using clients (pub/sub). And
neither should you be allowed to.
I guess we need more of such examples to understand correct use if admin
API.
Thanks,
On Tue, 1 Oct 2019 at 19:45, Sebastian Schmitz <
sebastian.schm...@propellerhead.co.nz> wrote:
> I didn'
I didn't change anything with the topic... But as it only affects one
topic my idea would be that it's related to the publisher as it's
different for this specific topic.
Can a publisher tell Kafka what to do about replication? Like having
such an influence to have this kind of symptoms?
Als
I was going to ask you to do that :) As long as >1 replicas are in-sync
Kafka handles this nicely for recreating everything in the restarted broker.
I am curious, do you remember manipulating something before all these
started? e.g. Using some topic admin command (or something along the line) ?
I deleted the topic now and with topic-auto-create enabled it was
immediately recreated and all is in sync again.
Will keep and eye on this to see if it happens again
On 30-Sep-19 3:12 PM, Sebastian Schmitz wrote:
Hello again,
after like 15 minutes I have now this result:
root@kafka_nod
Hello again,
after like 15 minutes I have now this result:
root@kafka_node_1:/opt/kafka_2.12-2.3.0/bin#
./kafka-reassign-partitions.sh --bootstrap-server localhost:9092
--zookeeper node1:2181 --reassignment-json-file move2.json --verify
Status of partition reassignment:
Reassignment of partit
Hello,
I just ran the kafka-reassign-partitions with --generate to create the
json and then with --execute to run it.
Now when checking with --verify I can see that the 4 partitions (it now
changed from only one partitions not having all in ISR to 12 not being
all in ISR) are successful, but t
hello,
Could you please try to run kafka-reassign-partitions with your topic
reassignment JSON? That doesn't require any restart, and should tell you if
any issues with reassignment. The examples are provided in Confluence wiki.
I would recommend that you do a "Describe" on your topic to ensure t
Hello,
I have one topic with 12 partitions where the partition 0 is missing one
node from ISR... Is there a way I get get it back to work again without
having to do some weird stuff like restarting the cluster?
Because this missing node in ISR is causing some problems for the
consumers...
Th
