[MCOL-1140] postConfigure fails to run on a system without a pm1 Created: 2018-01-05 Updated: 2023-10-26 Resolved: 2020-04-15 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ? |
| Affects Version/s: | 1.1.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | David Hill (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | community | ||
| Environment: |
non-root amazon ami 3 pm combo system with EBS |
||
| Description |
|
in testing failover based on a user scenario, ran into a situation where the system become unusable. First got the the problem in Then from pm3, did a shutdown and planned to rerun postConfigure to fix. But then I got the below error message.. so either need to document this issue that a pm1 server needs to be added back into the system or we change the logic where we require postConfigure from running on pm1. getst System Storage Configuration Performance Module (DBRoot) Storage Type = external DBRoot IDs unassigned = 1, 3 Amazon EC2 Volume Name/Device Name/Amazon Device Name for DBRoot2: vol-0f2fa799bd8450525, /dev/sdh, /dev/xvdh mcsadmin> shutd y This command stops the processing of applications on all Modules within the MariaDB ColumnStore System Checking for active transactions Stopping System... Shutting Down System... mcsadmin> exit This is the MariaDB ColumnStore System Configuration and Installation tool. IMPORTANT: This tool should only be run on the Parent OAM Module Prompting instructions: Press 'enter' to accept a value in (), if available or A copy of the MariaDB ColumnStore Configuration file has been saved during Package install. Do you want to utilize the configuration data from the saved copy? [y,n] > n ===== Setup System Server Type Configuration ===== There are 2 options when configuring the System Server Type: single and multi 'single' - Single-Server install is used when there will only be 1 server configured 'multi' - Multi-Server install is used when you want to configure multiple servers now or Select the type of System Server install [1=single, 2=multi] (2) > ===== Setup System Module Type Configuration ===== There are 2 options when configuring the System Module Type: separate and combined 'separate' - User and Performance functionality on separate servers. 'combined' - User and Performance functionality on the same server Select the type of System Module Install [1=separate, 2=combined] (2) > Combined Server Installation will be performed. NOTE: The MariaDB ColumnStore Schema Sync feature will replicate all of the MariaDB ColumnStore Schema Sync feature is Enabled, do you want to leave enabled? [y,n] NOTE: Configured to have ColumnStore use the Amazon AWS CLI Tools NOTE: MariaDB ColumnStore Replication Feature is enabled Enter System Name (1.1.2) > ERROR: exiting, postConfigure can only run executed on pm1, current module is pm3 |
| Comments |
| Comment by David Hill (Inactive) [ 2018-01-09 ] |
|
reproduced issue once I got a wortked 6.9 build machine start postConfigure and it hang waiting for system to startup, procmgr wasnt getting laucnhed mcsadmin> getsystemi System columnstore-1 System and Module statuses Component Status Last Status Change Module pm1 INITIAL MariaDB ColumnStore Process statuses Process Module Status Last Status Change Process ID Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0 Jan 9 20:33:00 ip-172-30-0-167 ProcessMonitor[15766]: 00.397406 |0|0|0| D 18 CAL0000: |
| Comment by David Hill (Inactive) [ 2018-01-25 ] |
|
a number of issue were found in oam code when a pm1 didnt exist, so this needs to be pushed to later release |
| Comment by David Hill (Inactive) [ 2018-01-29 ] |
|
Look at addressing this issue by changing a working pm to pm1 went pm1 goes bad.. |
| Comment by Todd Stoffel (Inactive) [ 2020-04-15 ] |
|
OAM is being deprecated and replaced by an enhanced API and the MaxScale orchestration project. |