Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-17524

MongoDB sharding problem

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 2.2.7
    • Internal Code, Sharding
    • None

    Description

      I have a mongoDB cluster of 3 replication sets

      Getting this error

      id_ObjectId('54f9ed416aad853b66d0c21f')", configdb: "172.31.12.107:27019,172.31.12.93:27019,172.31.12.43:27019" } result: { ok: 0.0, errmsg: "Error locking distributed lock for split. :: caused by :: 13651 error checking clock skew of cluster 172.31.12.107:27019,172.31.12.93:27019,172.31.12..

      Ntp time on these servers are all synced.

      output date of all servers

      mongo-s3:
      Tue Mar 10 18:47:41 IST 2015
      mongo-s2:
      Tue Mar 10 18:47:41 IST 2015
      mongo-rt1:
      Tue Mar 10 18:47:41 IST 2015
      mongo-p3:
      Tue Mar 10 18:47:41 IST 2015
      mongo-s1:
      Tue Mar 10 18:47:41 IST 2015
      mongo-p1:
      Tue Mar 10 18:47:41 IST 2015
      mongo-p2:
      Tue Mar 10 18:47:41 IST 2015

      I restarted the cluster keeping ntp up2date , but still same error.
      Please may I know what could be the problem ?

      Attachments

        Activity

          People

            randolph@mongodb.com Randolph Tan
            girmbhat Girish Bhat
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: