[bug] storaged may not fully stopped but script nebula.service tells that it's successfully stopped #1803
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
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.
The text was updated successfully, but these errors were encountered: