Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-6105

deactivate_only logic is always enabled on node removal in CMAPI

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • cmapi
    • None

    Description

      `ClusterHandler.remove_node` calls node_manipulation:remove_node. The latter takes deactivate_only parameter, which is True be default. Currently there are no places in the code that pass deactivate_only=False.
      It means that we never remove nodes from DesiredNodes/InactiveNodes/ReadOnlyNodes.
      It is very strange. If we decide that this is the correct behavior, we must remove deactivate_only parameter, because it is essentially fixed and only complicates the logic

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MCOL-5861 Read-only Columnstore node

          • Major - Major loss of function.
          • In Progress

          Activity

            People

              alan.mologorsky Alan Mologorsky
              AlexanderPresniakov Alexander Presniakov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.