Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server: remove the disturbing log when store is tombstone #1382

Merged
merged 4 commits into from
Dec 19, 2018

Conversation

rleungx
Copy link
Member

@rleungx rleungx commented Dec 13, 2018

What problem does this PR solve?

Currently, when there is tombstone store, it will print the log [info] buried store id:x address:"xxx" state:Tombstone every minute, which is kind of disturbing.

What is changed and how it works?

This PR removes this unused log and makes some cleanup.

Check List

Tests

  • Manual test (make test)

Signed-off-by: rleungx <rleungx@gmail.com>
@rleungx rleungx added the type/enhancement The issue belongs to an enhancement. label Dec 13, 2018
@rleungx
Copy link
Member Author

rleungx commented Dec 14, 2018

/run-unit-test

1 similar comment
@rleungx
Copy link
Member Author

rleungx commented Dec 14, 2018

/run-unit-test

@disksing disksing added the needs-cherry-pick-release-2.1 The PR needs to cherry pick to release-2.1 branch. label Dec 17, 2018
server/cluster.go Outdated Show resolved Hide resolved
@disksing
Copy link
Contributor

Please cherry-pick it to release-2.1

@rleungx rleungx merged commit 321b909 into tikv:master Dec 19, 2018
rleungx added a commit to rleungx/pd that referenced this pull request Dec 19, 2018
* remove the disturbing log when the store is tombstone

Signed-off-by: rleungx <rleungx@gmail.com>
rleungx added a commit that referenced this pull request Dec 19, 2018
)

* remove the disturbing log when the store is tombstone

Signed-off-by: rleungx <rleungx@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-2.1 The PR needs to cherry pick to release-2.1 branch. type/enhancement The issue belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants