[MCOL-2231] Partial availability for data with unavailable dbroots/extents Created: 2019-03-12  Updated: 2023-07-02  Resolved: 2023-07-02

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: None
Fix Version/s: Icebox

Type: New Feature Priority: Major
Reporter: Roman Assignee: Todd Stoffel (Inactive)
Resolution: Won't Do Votes: 1
Labels: None


 Description   

Consider the situation. CS cluster has N PM modules with M dbroots each. On PM went down so we have N-1*M dbroots with data. With current version of CS this data is currently inaccessable. This could be reproduced using official CS Zeppelin images. There are at least two errors reported when one of PM-s in 2UM2PM scenario went down:

  • ERROR 1815 (HY000): Internal error: InetStreamSocket::readToMagic: Remote is closed
  • ERROR 1815 (HY000): Internal error: st: 0 TupleBPS::sendPrimitiveMessages() caught an exception: IDB-2034: At least one DBRoot required for that query is offline.

One should investigate the reason behind the errors and enable partial data availability.

 Comments   
Comment by Todd Stoffel (Inactive) [ 2023-07-02 ]

The "create date" on this ticket is pre-convergence with MariaDB server. If the issue still exists in a modern version of the engine/plugin please submit a new ticket.

Generated at Thu Feb 08 02:34:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.