A DevOps Engineer needs to change the default size for a tar file to 512 MB. Which option should be used to enable this configuration?

A DevOps Engineer needs to change the default size for a tar file to 512 MB. Which option should be used to enable this configuration?

• A. Set changesSize property to 512 in org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService.config file
• B. Set tarmk.size property to 512 in org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config file
• C. Set Segment Cache Size property to 512 in Oak Segment TAR NodeStore Service configuration in Webconsole
• D. Set NodeState Cache property to 512 in Apache Jackrabbit Oak Document NodeStore Service configuration in Webconsole.

Answer: (B)

Configuring the size of TAR files used by TarMK in the Segment NodeStore is controlled by the tarmk.size parameter in the SegmentNodeStoreService.config file. Setting tarmk.size to 512 means TAR files will be capped at 512 MB, so TarMK will roll over to a new TAR file once the current one reaches that limit. This setting directly impacts how data is organized on disk for the TarMK segment store. Other options relate to caching or to the DocumentNodeStore, which do not affect the size of TAR files. The cache-related settings optimize in-memory performance, not the on-disk TAR file size.

Configuring the size of TAR files used by TarMK in the Segment NodeStore is controlled by the tarmk.size parameter in the SegmentNodeStoreService.config file. Setting tarmk.size to 512 means TAR files will be capped at 512 MB, so TarMK will roll over to a new TAR file once the current one reaches that limit. This setting directly impacts how data is organized on disk for the TarMK segment store.

Other options relate to caching or to the DocumentNodeStore, which do not affect the size of TAR files. The cache-related settings optimize in-memory performance, not the on-disk TAR file size.