Dear all,
On our development cluster we have a topic which only has a single replica.
Since creating it we lost a node. By using the kafka-topics -describe command I
can see that where the replica was on the lost node (broker #404), the leader
has now become "-1".
Topic: alpha Partition: 0 Leader: 399 Replicas: 399
Isr: 399
Topic: alpha Partition: 1 Leader: 400 Replicas: 400
Isr: 400
Topic: alpha Partition: 2 Leader: 402 Replicas: 402
Isr: 402
Topic: alpha Partition: 3 Leader: 403 Replicas: 403
Isr: 403
Topic: alpha Partition: 4 Leader: -1 Replicas: 404
Isr: 404
Topic: alpha Partition: 5 Leader: 405 Replicas: 405
Isr: 405
Topic: alpha Partition: 6 Leader: 406 Replicas: 406
Isr: 406
Topic: alpha Partition: 7 Leader: 398 Replicas: 398
Isr: 398
Topic: alpha Partition: 8 Leader: 399 Replicas: 399
Isr: 399
Topic: alpha Partition: 9 Leader: 400 Replicas: 400
Isr: 400
Topic: alpha Partition: 10 Leader: 402 Replicas: 402
Isr: 402
Topic: alpha Partition: 11 Leader: 403 Replicas: 403
Isr: 403
Topic: alpha Partition: 12 Leader: -1 Replicas: 404
Isr: 404
Topic: alpha Partition: 13 Leader: 405 Replicas: 405
Isr: 405
Topic: alpha Partition: 14 Leader: 406 Replicas: 406
Isr: 406
Topic: alpha Partition: 15 Leader: 398 Replicas: 398
Isr: 398
I ran the ReassignPartitionsCommand, and set the broker list to
"403,405,406,400,399,402,398" to reassign them away from 404 but the
reassignments have been in-progress for quite a while now. Does broker 404 need
to be up and alive to allow the reassignment to complete? Or can the
reassignment occur without 404 being up and well and I'm therefore being
impatient?
The updated kafka-topics output is now:
Topic: alpha Partition: 0 Leader: 398 Replicas: 398
Isr: 398
Topic: alpha Partition: 1 Leader: 400 Replicas: 403,400
Isr: 400
Topic: alpha Partition: 2 Leader: 405 Replicas: 405
Isr: 405
Topic: alpha Partition: 3 Leader: 406 Replicas: 406
Isr: 406
Topic: alpha Partition: 4 Leader: -1 Replicas: 400,404
Isr: 404
Topic: alpha Partition: 5 Leader: 399 Replicas: 399
Isr: 399
Topic: alpha Partition: 6 Leader: 402 Replicas: 402
Isr: 402
Topic: alpha Partition: 7 Leader: 398 Replicas: 398
Isr: 398
Topic: alpha Partition: 8 Leader: 403 Replicas: 403
Isr: 403
Topic: alpha Partition: 9 Leader: 400 Replicas: 405,400
Isr: 400
Topic: alpha Partition: 10 Leader: 406 Replicas: 406
Isr: 406
Topic: alpha Partition: 11 Leader: 403 Replicas: 400,403
Isr: 403
Topic: alpha Partition: 12 Leader: -1 Replicas: 399,404
Isr: 404
Topic: alpha Partition: 13 Leader: 402 Replicas: 402
Isr: 402
Topic: alpha Partition: 14 Leader: 398 Replicas: 398
Isr: 398
Topic: alpha Partition: 15 Leader: 403 Replicas: 403
Isr: 403
Many thanks,
Michael
Michael Griffiths
System Developer
BAE Systems Applied Intelligence
___________________________________________________________
| E: michael.griffit...@baesystems.com
BAE Systems Applied Intelligence, Surrey Research Park, Guildford, Surrey, GU2
7RQ.
www.baesystems.com/ai<http://www.baesystems.com/ai>
Please consider the environment before printing this email. This message should
be regarded as confidential. If you have received this email in error please
notify the sender and destroy it immediately. Statements of intent shall only
become binding when confirmed in hard copy by an authorised signatory. The
contents of this email may relate to dealings with other companies under the
control of BAE Systems Applied Intelligence Limited, details of which can be
found at http://www.baesystems.com/Businesses/index.htm.
