ok, sounds like an issue. Can you do me a favor please? Try to duplicate this but this time wait a full 2 minutes between changes. It's possible mongo changes are just catching up with each other or a race condition.
On Wed, Jun 27, 2012 at 9:21 AM, Kumaran <[email protected]> wrote: > Sorry,Its my bad...Its should be distributed DB arbiter and not Distributed > DB(I mentioned it wrongly as Distributed DB instead of Distributed DB > arbiter ).... > > Regards, > Kumaran T > > > On 6/27/2012 3:35 PM, Kumaran wrote: >> >> Hi Douglas, >> The issue is when we change Distributed DB from primary server to >> secondary server and shutdown primary server then mongo db in secondary is >> still showing as secondary..But If we sent profiles once Distributed DB >> changed from primary server to secondary server then its works fine.. >> >> Regards, >> Kumaran T >> >> >> On 6/27/2012 3:29 PM, Douglas Hubler wrote: >>> >>> disabling mongo db from primary shouldn't be allowed for variety of >>> reasons i could detail if you're really interested, but in short >>> please update the issue w/that note. thanks >>> >>> On Wed, Jun 27, 2012 at 2:42 AM, Kumaran >>> <[email protected]> wrote: >>>> >>>> Hi All, >>>> If we change Distributed DB from primary to secondary server whether we >>>> want give sent profiles? Because in my case Secondary server mongo is >>>> still >>>> showing as Secondary When I changed Distributed DB from primary to >>>> secondary and bring down the master...Once I bring up master both the >>>> server >>>> mongo will be secondary....So we want send profiles and reboot the >>>> servers... >>>> >>>> Note: >>>> If I sent profiles to server once I changed Distributed DB from >>>> primary to >>>> secondary server then everything works fine... >>>> >>>> Regards, >>>> Kumaran T >>>> > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
