[MCOL-870] redistributeData seems possible after suspendDatabaseWrites Created: 2017-08-11 Updated: 2022-11-05 Resolved: 2022-11-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | writeengine |
| Affects Version/s: | 1.0.10 |
| Fix Version/s: | Icebox |
| Type: | Task | Priority: | Major |
| Reporter: | MG | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Description |
|
This may be just cosmetic or actually safe design decision. I am unsure if the following flow would result in a clean copy of dbroots:
|
| Comments |
| Comment by David Thompson (Inactive) [ 2017-08-11 ] |
|
It is documented and recommended to suspend writes before doing a redistribute. We decided it was better and more explicit to not have redistribute do this automatically. I think in your case you are asking if one admin were to suspend writes in order to do a snapshot for a backup and another admin concurrently runs a redistribute? If so I think it's safe to say this would not be recommended. Redistribute writes the new data as a copy in it's new location before removing the old. In certain cases you may be safe but i think better to have coordination around this, especially redistribute. |
| Comment by Todd Stoffel (Inactive) [ 2022-11-05 ] |
|
This item is being closed because it was well passed the expiration date with no activity. If you suspect this was done in error please create a new ticket. |