Sean Fellows created KAFKA-2535:
-----------------------------------
Summary: When removing a partition from an out of sync broker, it
should not need to join the ISR first
Key: KAFKA-2535
URL: https://issues.apache.org/jira/browse/KAFKA-2535
Project: Kafka
Issue Type: Improvement
Components: replication
Affects Versions: 0.8.2.0
Reporter: Sean Fellows
Assignee: Neha Narkhede
Priority: Minor
I'm not 100% sure this improvement would be legitimate, but I will describe the
issue I have been seeing and hopefully folks can advise.
To reproduce:
1. Start with a broker that is out of sync for a particular partition.
2. Issue a reassignment that moves that partition off of that broker.
Observed behavior:
The broker continues replicating until it joins the ISR.
Desired behavior:
It seems to me that this broker should stop replication immediately. If this
broker is able to replicate from somewhere, it means the ISR is not empty, so
it should be safe to delete this partition's data from this broker.
The reason I am interested in this is that I would like to be able to reduce
disk usage on a broker by removing partitions from it. But if it has fallen
behind on replication it continues to need *more* disk space until it has
caught up. But it is just going to delete this data anyway, so it seems like
this optimization should be possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
