Tar file naming conventions
The tar files used by AEM in the repository/segmentstore have names like dataNNNNNL.tar, where NNNNN is a 5 digit number and L is a letter. What happens when NNNNN needs to be greater than 99999?
The tar files used by AEM in the repository/segmentstore have names like dataNNNNNL.tar, where NNNNN is a 5 digit number and L is a letter. What happens when NNNNN needs to be greater than 99999?
Hi,
Can you please check below if it helps:
Oak TAR file layout
A few words on how Oak names TAR files. The convention is to always start with a data00000a.tar file. As data is written to the repository, new TAR files are added with increasing numbers, thus ending up with data00001a.tar, data00002a.tar and so on.
Each time a compaction cycle ends, there is a cleanup phase in which segments from an old generation are purged. Those tar files that shrink by at least 25% are rewritten to a new tar generation, skipping the reclaimed segments. A shrunk TAR file increases its tail generation character, e.g. from data00000a.tar to data00000b.tar.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.