[MCOL-1509] OAM needs to check the DDL/DML Ip addresses to make sure they match Created: 2018-06-27 Updated: 2023-10-26 Resolved: 2020-04-15 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ? |
| Affects Version/s: | 1.1.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2018-15, 2018-16, 2018-17, 2018-18, 2018-19, 2018-20, 2018-21 |
| Description |
|
Customer reported an error in create table with DDLProc connection lost, but DDLProc wasnt crashing, but the Ip address for DDLProc was pointing to UM2. But UM1 was the master and DMLProc was pointing to UM1. So need to add in the oam code at startup a validation to check these ip addresses and get them insync, if they are out of sync.. |
| Comments |
| Comment by David Hill (Inactive) [ 2018-08-07 ] |
|
how to test. 1. Do any type of system install and get the system to ACTIVE state. |
| Comment by David Hill (Inactive) [ 2018-09-04 ] |
|
Fix is in branch |
| Comment by David Hill (Inactive) [ 2018-09-14 ] |
|
tried these with no avail: 1. sleep after the config write no luck, updates made by setUMProcIPs functions just aren't getting maintained. |
| Comment by Todd Stoffel (Inactive) [ 2020-04-15 ] |
|
OAM is being deprecated and replaced by an enhanced API and the MaxScale orchestration project. |