[MCOL-3611] Make sure oam does the right thing on failover with S3 Created: 2019-11-12 Updated: 2021-04-19 Resolved: 2020-12-17 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | Storage Manager |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Patrick LeBlanc (Inactive) | Assignee: | Ben Thompson (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
C7, gluster vol replicating the whole 'storagemanager' directory for each node, fake-cloud configuration |
||
| Issue Links: |
|
||||||||||||
| Description |
|
To get in front of failover problems the Sky team might encounter, we need to test the scenario where a node goes down. So, set up a multiple-pm cluster to use S3 (can be VMs on a local box, doesn't matter), use gluster as the DFS to replicate & make available all data under SM's storage dir, get things running then nuke a node and see what happens. The Storagemanager stuff should be able to handle it, the question is mainly whether ProcMon/Mgr are going to do the right thing, and consistently. It hasn't been tested yet but we think it should work. |
| Comments |
| Comment by Ben Thompson (Inactive) [ 2020-12-17 ] |
|
OAM removed from product this is N/A |