Just to report in case anyone finds this via a web search.
I did the following:
rmr brokers/topics/mytopic
rm admin/delete_topics/mytopic
and it worked fine. The broker reported an exception in `kafka-controller.log`
after the last rm ran but it still ran without any problems.
I
The broker id wasn't reused no, it's a new id.
Unfortunately we can't afford bringing down the cluster, I'll have to do this
with the cluster online.
On Mon, Dec 16, 2019, at 17:27, Peter Bukowinski wrote:
> If it was replaced, and a new broker was brought online with the same
> id, wherever
If it was replaced, and a new broker was brought online with the same id,
wherever topic partitions had been previously assigned to it should have been
recreated.
At this point, however, I would shut down the cluster, delete the znodes,
delete the topic directories from the brokers, then bring
It doesn't exist anymore, we replaced it after a hardware failure.
Thinking about it I don't think I reassigned the partitions for broker 5 to the
new broker before deleting these topics, I didn't realize that it was necessary
for all brokers to be online.
Since broker 5 is never coming back
If any brokers are offline, kafka can’t successfully delete a topic. What’s the
state of broker 5?
-- Peter (from phone)
> On Dec 13, 2019, at 8:55 AM, Vincent Rischmann wrote:
>
> Hi,
>
> I've deleted a bunch of topics yesterday on our cluster but some are now
> stuck in "marked for
Hi,
I've deleted a bunch of topics yesterday on our cluster but some are now stuck
in "marked for deletion".
* i've looked in the data directory of every broker and there's no data left
for the topics, the directory doesn't exist anymore.
* in zookeeper the znode `brokers/topics/mytopic` still
