Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-15102

Determine cause of auto-failover following a time forward jump

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • feature-backlog
    • 2.5.1, 3.0, 4.0.0
    • ns_server
    • Security Level: Public
    • Untriaged
    • Unknown

    Description

      In CBSE-1842, "Detected time forward jump (or too large erlang scheduling latency)" on master (198) led to it auto-failing over node 205.

      Through code inspection, it is not clear how the time jump could cause the auto-failover. The issue is most likely not in ns_server code.
      Aliaksey thinks we need to look deeper into Erlangs's distributed communication - probably it gets stuck due to time jump.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            ajit.yagaty Ajit Yagaty [X] (Inactive)
            poonam Poonam Dhavale
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty