Subscribe to Posts by Email

Subscriber Count

    696

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

MongoDB for Oracle DBA’s Part 10 : Switchover & Role Transition between Primary and Secondary

In MongoDB as like Oracle Dataguard switchover is possible to but in different way.

You can ask Primary to stepdown and let nodes elect a new primary in replicaset. This can be done using rs.stepDown() method.

Before stepping down primary, one must know the below

  • The procedure blocks all writes to primary while it runs
  • Terminates all sessions and running jobs, index rebuilts etc
  • Disconnects all connections
  • If the wait period to elect a new primary exceeds then primary will not step down.

Let's take a look of the same,

  1. I have opened three sessions and in one sessions querying a table which is running (the right top most one in screenshot)
  2. In another session tail the log file so can understand what happens when a step down is initiated
  3. In the session that left side , initiated the stepdown of primary , immediately disconnects the current session and also the session that running a query on the database (top left side)
  4. In the log it shows the primary is transitioning to secondary
  5. as per rs.status() the 47018 (original primary) becomes secondary.

Screenshot

 

Comments are closed.