errose28 commented on PR #5106: URL: https://github.com/apache/ozone/pull/5106#issuecomment-1648749749
> Also, to summarize the issue @devmadhuu found, the bootstrapper was using this method: ServerUtils.getOzoneMetaDirPath() to determine the path of the metadir. It turns out that in some configurations that method doesn't seem to work as expected. Yeah I think most/all of our docker tests don't set om.db.dirs and just rely on ozone.metadata.dirs as the fallback. In a real deployment om.db.dirs would be set and that is where all the RocksDB info would be. `OMStorage#getOmDbDir` can be used instead of `ServerUtils#getOzoneMetaDirPath` to account for this. I think the way it is done here is fine though, since the location is already stored in the `DBCheckpoint` object. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
