[GitHub] [ozone] sumitagrawl commented on pull request #3801: HDDS-7284. JVM crash for rocksdb for read/write after close

[GitBox <gi...@apache.org>]

sumitagrawl commented on PR #3801:
URL: https://github.com/apache/ozone/pull/3801#issuecomment-1274084098

   > @sumitagrawl , thanks for reporting and fixing this issue. Since JVM is crashed for there is still read/write after close, which means there is some issue with current Recon code, threads that read/write rocksdb should be stopped before rocksdb close. Can we try to do that first? We should guarantee close RocksDB at the end, than adding a layer of mechanism to mitigate the code issue.
   > 
   > Regarding two solutions, I would prefer solution two, because you cannot make sure how long the wait time is enough for solution one.
   
   As discussed, 
   1. Solution 1 is done to avoid the crash of integration test, till graceful shutdown is properly implemented and without performance impact.
   2. Graceful shutdown for Recon needs to be created but its low priority one


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org