Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-5789

race between rpl_parallel_change_thread_count and slave start upon server start without --skip-slave-start

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.8
    • 10.0.9
    • None
    • None

    Description

      Reported on maria-developers@ by nanyi607rao:

      Second is in rpl_parallel_change_thread_count()

      I think it need add mysql_cond_broadcast(&pool->COND_rpl_thread_pool) after all new threads are ok, this is for
      the case that skip_slave_start=OFF,then SQL thread would start automaticlly, it could wait forever in rpl_parallel_thread_pool::get_thread(), because SQL thread may reach this function before another thread reach the rpl_parallel_change_thread_count().

      Attachments

        Activity

          knielsen Kristian Nielsen created issue -
          knielsen Kristian Nielsen made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]

          Pushed to 10.0

          knielsen Kristian Nielsen added a comment - Pushed to 10.0
          knielsen Kristian Nielsen made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow defaullt [ 35808 ] MariaDB v2 [ 43105 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 43105 ] MariaDB v3 [ 62155 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 62155 ] MariaDB v4 [ 147588 ]

          People

            knielsen Kristian Nielsen
            knielsen Kristian Nielsen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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