Fix a file sync storage crash for ca-data.git after adding certificates in Puppet Enterprise 2018.1 and 2019.0 and later
Did this solve your problem?
0 out of 0 found this helpful
When you add many certificates as part of a migration, upgrade, or maintenance, file sync storage might crash causing code deployment to fail and Puppet Server to crash.
Any certificates that you a...
Comments
4 comments
Hi Mahesh,
Is the default value 1024MB (1GB) or 1024KB (1MB)? Your feedback above:
By default, the
stream-file-threshold
parameter of jgit is configured as 1024 (1MB) in PE 2018.1.13 and later versions. In previous versions, it's configured as 512MB.is contradicting.
Kindly confirm if the default value is in MB or KB?
Regards,
Avikal Jain
I would guess 1GB (not 1MB), I will ask Mahes to confirm.
I confirmed with one of my other teammates that this should read: In previous versions, it's configured as 512KB.
I will go ahead and update that in the text of the article, apologies for the wait.
Not a problem, thanks for clarification.
We got further statistics from Puppet support on what this value should inline with number of nodes for others to refer:
For a 1MB threshold, we could have at maximum the following number of certificates at the associated certname length (+.pem).
10 character certnames: 24966
15 character certnames: 22310
20 character certnames: 20164
40 character certnames: 14562
60 character certnames: 11396
100 character certnames: 7942
Thus, it is actually impacted by the length of certname as well as number of certs. If your average certname is around 20 characters, setting file_sync_stream_file_threshold=1536 should be sufficient for 25k nodes.
Regards,
Avikal Jain
Please sign in to leave a comment.