Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
1.4.0
-
None
Description
Build tested: 1.4.0-1
server commit:
67452bc
engine commit:
64ceb86
The ColumnStore packages comes with a storageManager.cnf file that has been configured to use "localStorage" type. If S3 cloud storage is desired, the storageManager.cnf file must be configured property before running postConfigure.
For S3 cloud storage, distributed installation with multi-nodes, postConfigure does not distribute the storageManager.cnf file from PM1 to other nodes. The stack would end up with S3 on PM1 and localStorage on other PMs. I tried putting storageManager.cnf in other nodes manually before running postConfigure. This work around does not work because when postConfigure installs the MCS packages on remote nodes, my version of the storageManager.cnf gets overwritten.
We should distributed the storageManager.cnf file, just like it does for other DBRM files, at the beginning of the start system process.