*Description of changes: Updated chain header per conversation with jfrog support. Having this commented out is causing caching on the /data mount to fill and crash the node. By making this change files will correctly cache in S3. Further info can be found at the following link:
Issue #, if available:
*Description of changes: Updated chain header per conversation with jfrog support. Having this commented out is causing caching on the /data mount to fill and crash the node. By making this change files will correctly cache in S3. Further info can be found at the following link:
https://www.jfrog.com/confluence/display/JFROG/Configuring+the+Filestore#ConfiguringtheFilestore-AmazonS3SDKClusterBinaryProvider
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.