[MCOL-1345] workernode and primproc should not be started on newly added PMs Created: 2018-04-17 Updated: 2023-10-26 Resolved: 2019-07-10 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ? |
| Affects Version/s: | 1.1.4 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Minor |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Build tested: 1.1.4-1 Started with a 1um2pm stack, I performed the following steps to add two PM modules: 1. Adddbroot (2) The newly added PMs have the following status ProcessMonitor pm3 ACTIVE Tue Apr 17 20:44:03 2018 14725 ProcessMonitor pm4 ACTIVE Tue Apr 17 20:44:06 2018 14587 |