The --nojournal option has been completely removed, so this should be reflected in the documentation.

Additionally, the intermediate step starting up mongod with --nojournal when changing the WT journal compressor is not required, only a clean shutdown and startup is required. The step was "required" due to a bug fixed by WT-8652, in which even on clean shutdown checkpoint metadata was not stored properly. This caused journal recovery to always try to decompress entries, as WT thought that there were entries pending to be recovered. The nojournal step coincidentally fixed the issue because it deletes the contents of the journal directory, hence on the following startup with a different compressor the WT did not manifest because there were no journal files.

https://www.mongodb.com/docs/manual/tutorial/manage-journaling/#change-wiredtiger-journal-compressor

Description of Linked Ticket

Determine the potential use cases for the nojournal option on the WT storage engine and investigate the potential deprecation of the option