[
https://issues.apache.org/jira/browse/KAFKA-8738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dingsainan updated KAFKA-8738:
--
Description:
Hi,
I am experiencing one situation that the log cleaner dose not work for the
related topic-partition when using --kafka-reassign-partitions.sh tool for
V2.1.1 for more than one time frequently.
My operation:
submitting one task for migration replica in one same broker first, when the
previous task still in progress, we submit one new task for the same
topic-partition.
{code:java}
// the first task:
{"partitions":
[{"topic": "lancer_ops_billions_all_log_json_billions",
"partition": 1,
"replicas": [6,15],
"log_dirs": ["any","/data/mnt/storage02/datum/kafka_data"]}]
}
//the second task
{"partitions":
[{"topic": "lancer_ops_billions_all_log_json_billions",
"partition": 1,
"replicas": [6,15],
"log_dirs": ["any","/data/mnt/storage03/datum/kafka_data"]}]
}
{code}
My search:
Kafka executes abortAndPauseCleaning() once task is submitted, shortly,
another task is submitted for the same topic-partition, so the clean thread
status is {color:#ff}LogCleaningPaused(2){color} currently. When the second
task completed, the clean thread will be resumed for this topic-partition once.
In my case, the previous task is killed directly, no resumeClean() is executed
for the first task, so when the second task is completed, the clean status for
the topic-partition is still {color:#ff}LogCleaningPaused(1){color}, which
blocks the clean thread for the topic-partition.
_That's all my search, please confirm._
_Thanks_
_Nora_
was:
Hi,
I am experiencing one situation that the log cleaner dose not work for the
related topic-partition when using --kafka-reassign-partitions.sh tool for
V2.1.1 for more than one time frequently.
My operation:
submitting one task for migration replica in one same broker first, when the
previous task still in progress, we submit one new task for the same
topic-partition.
My search:
Kafka executes abortAndPauseCleaning() once task is submitted, shortly, another
task is submitted for the same topic-partition, so the clean thread status is
{color:#ff}LogCleaningPaused(2){color} currently. When the second task
completed, the clean thread will be resumed for this topic-partition once. In
my case, the previous task is killed directly, no resumeClean() is executed for
the first task, so when the second task is completed, the clean status for the
topic-partition is still {color:#ff}LogCleaningPaused(1){color}, which
blocks the clean thread for the topic-partition.
_That's all my search, please confirm._
_Thanks_
_Nora_
> Cleaning thread blocked when more than one ALTER_REPLICA_LOG_DIRS requests
> sent
>
>
> Key: KAFKA-8738
> URL: https://issues.apache.org/jira/browse/KAFKA-8738
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: dingsainan
>Priority: Major
>
> Hi,
>
> I am experiencing one situation that the log cleaner dose not work for the
> related topic-partition when using --kafka-reassign-partitions.sh tool for
> V2.1.1 for more than one time frequently.
>
> My operation:
> submitting one task for migration replica in one same broker first, when
> the previous task still in progress, we submit one new task for the same
> topic-partition.
>
> {code:java}
> // the first task:
> {"partitions":
> [{"topic": "lancer_ops_billions_all_log_json_billions",
> "partition": 1,
> "replicas": [6,15],
> "log_dirs": ["any","/data/mnt/storage02/datum/kafka_data"]}]
> }
> //the second task
> {"partitions":
> [{"topic": "lancer_ops_billions_all_log_json_billions",
> "partition": 1,
> "replicas": [6,15],
> "log_dirs": ["any","/data/mnt/storage03/datum/kafka_data"]}]
> }
>
> {code}
>
> My search:
> Kafka executes abortAndPauseCleaning() once task is submitted, shortly,
> another task is submitted for the same topic-partition, so the clean thread
> status is {color:#ff}LogCleaningPaused(2){color} currently. When the
> second task completed, the clean thread will be resumed for this
> topic-partition once. In my case, the previous task is killed directly, no
> resumeClean() is executed for the first task, so when the second task is
> completed, the clean status for the topic-partition is still
> {color:#ff}LogCleaningPaused(1){color}, which blocks the clean thread for
> the topic-partition.
>
> _That's all my search, please confirm._
>
> _Thanks_
> _Nora_
--
This message was sent by Atlassian JIRA
