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

[bug] storaged may not fully stopped but script nebula.service tells that it's successfully stopped #1803

Closed
whitewum opened this issue Feb 22, 2020 · 2 comments
Assignees
Labels
need to discuss Solution: issue or PR without a clear conclusion on whether to handle it type/enhancement Type: make the code neat or more efficient

Comments

@whitewum
Copy link
Contributor

whitewum commented Feb 22, 2020

When I use nebula.service stop/start/restart to stop and start storaged,
I find in some cases (about 1 in 4 or 5 times), the script tells me storaged is stopped, but actually, the storaged process is running (maybe state Z or D).

I think it's because rocksdb is flushing data when exiting (I was doing bulk writing meanwhile stopping storaged), either the port or pid file release sequence is not correct.

@whitewum whitewum changed the title storaged may not fully stopped when script nebula.service restart [bug] storaged may not fully stopped but script nebula.service tells that it's successfully stopped Feb 22, 2020
@ownthink
Copy link

ownthink commented Feb 24, 2020

可以参考这个,有时候异常停止的时候等待一段时间,也不会退出,#1789

@whitewum
Copy link
Contributor Author

image

@CPWstatic CPWstatic added the need to discuss Solution: issue or PR without a clear conclusion on whether to handle it label Aug 27, 2021
@Sophie-Xie Sophie-Xie added the type/enhancement Type: make the code neat or more efficient label Aug 30, 2021
@whitewum whitewum closed this as completed Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need to discuss Solution: issue or PR without a clear conclusion on whether to handle it type/enhancement Type: make the code neat or more efficient
Projects
None yet
Development

No branches or pull requests

5 participants