GitHub user soumyajit-sahu opened a pull request:
https://github.com/apache/kafka/pull/1716
KAFKA-3123: Make abortAndPauseCleaning() a no-op when state is already
LogCleaningPaused
The function of LogCleanerManager.abortAndPauseCleaning() is to mark a
TopicAndPartition as LogCleaningPaused. Hence, it should be a no-op when the
TopicAndPartition is already in that state.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Microsoft/kafka
ignoreLogCleaningPauseRequestWhenAlreadyInPausedState
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1716.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1716
----
commit 3ad294377eee6e6ad3fdb47b7220dcb0913f1fc9
Author: Som Sahu <sos...@microsoft.com>
Date: 2016-08-10T00:45:55Z
Make abortAndPauseCleaning a no-op when state is already LogCleaningPaused
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
