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

How to copy the data between monogdb instance in incremental model without using replication set up

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.5.4
    • Component/s: MapReduce
    • Labels:
      None

      Hi All,

      I have replication set up like primary, secondary, arbitary.I am using the map/reduce concept for some queries in reporting module.I have few questions here.
      I am sending the report related queries to secondary replica , set readPreference as secondary in connection level.So if we have map/reduce in query it creates temporary collection on primary.After creating collection on primary again making the query to that collection.Actually my read preference set to secondary it goes to secondary at that time if the data has not synchronized to secondary i won't get any thing right ?My reports are taking huge time since i having the lot of data.
      And also i am having another question
      I want maintain another independent mongod process (server).So I want to copy the data from the other server( above replication set up) in once in a day.So i can send my report related requests to this independent server.If i use map/reduce on this server , create temporary collection on it only since it does not have any replication set up .But how can i copy the updated to the independent server like how synchronize the data in replication.Once in a day we can copy whole data to the independent server using the copydatabase, clone command but it is taking much time to copy.I want to copy the data only newly updated , inserted records to independent server like replication only.

      So i can resolve this problems?

            Assignee:
            Unassigned Unassigned
            Reporter:
            satheesh satheesh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: