[MCOL-3328] Need to disable distributed installation for non-root user as it is no longer supported Created: 2019-05-23 Updated: 2019-10-30 Resolved: 2019-10-30 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Build tested: 1.2.4-1 1st RC The default installation mode for postConfigure is non-distributed. There is an optional "-d" switch to indicate distributed installation mode. But distributed installation for non-root user is no longer supported. Therefore, we need to disable this installation combination. Otherwise, installation would still complete, but ColumnStore log directory will not be created and logging will not be setup. When running postConfigure, if distributed installation is specified for non-root user, we should output a messages stating that such installation is not support and abort post configuration. |
| Comments |
| Comment by David Hill (Inactive) [ 2019-05-23 ] |
|
"But distributed installation for non-root user is no longer supported. " This will be a Problem on Amazon AMI systems that have upgraded there software. Scenario: 1. Customer creates a system with 1.1.6 AMI. So if distributed install is disabled for non-root users, then that new node will fail to startup because it will be detested that a different version is installed. So now as part of the install procedure, they will need to install the binary themselves as part of the addModule function. So this will make things a lot more tidious to to addMdoule if you go this route, or make an exception for Amazon AMI Installs and continue to support distributed install |
| Comment by David Hill (Inactive) [ 2019-05-23 ] |
|
To me, this is just a procedural issue.. The user can still run the syslog setup as root user after postConfigure is completed on the other nodes. They need to do the same after addModule. This was a know procedure when 1.2.3 was released, that is why a new JIRA was opened to write our own logging functions.. David |
| Comment by Ben Thompson (Inactive) [ 2019-10-09 ] |
|
Might not be an issue anymore but you were just fixing other bugs with removing the -d option |
| Comment by Daniel Lee (Inactive) [ 2019-10-30 ] |
|
The issue has been fixed by |