Hi Mircea, Thanks......I will keep a track to it... Regards, Kumaran T
Mircea Carasel wrote: > > > On Wed, May 11, 2011 at 8:22 AM, Kumaran > <[email protected] > <mailto:[email protected]>> wrote: > > Hi Mircea, > So can I open Jira for it or wait for others opinion? > > :) I was hoping to get more opinions. Let's wait some more, we need > consensus for this in order for the ticket to be taken into consideration > Mircea > > > > Regards, > Kumaran T > > Mircea Carasel wrote: > > > > On Tue, May 10, 2011 at 4:06 PM, Kumaran > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > Hi Mircea, > Thanks for your update.....If this enhancement is posted > in Jira > means then can you please reply the issue no.I will keep a > track > on it.... > > The issue number is XX-9554, but as George Pointed out we > should not wait for a replication to take place in order > to raise alarm that mongo is down. As he says, supervisor > should monitor this. > > I would vote for a new JIRA, as I think that monitoring mongo > is important. Opinions? > > Regards, > Kumaran T > > > Mircea Carasel wrote: > > > > > > On Tue, May 10, 2011 at 3:30 PM, Kumaran > > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > > > Hi All, > > Now all the replication is shifted to Mongod.So when > mongod is down > > there will be a replication error message.So Alarm > will be a > good > > idea...So Alarm can be provided when Mongod is down > to the > Admin.. > > > > Yes, correct. I posted a patch that, among other > enhancements, > raises > > alarms for replication failures - including the case when > mongo is > > down. It is still in pending review > > Mircea > > > > > > Regards, > > Kumaran T > > > > > > > > _______________________________________________ > > sipx-dev mailing list > > [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> > > List Archive: > http://list.sipfoundry.org/archive/sipx-dev/ > > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > sipx-dev mailing list > > [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > _______________________________________________ > sipx-dev mailing list > [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > ------------------------------------------------------------------------ > > _______________________________________________ > sipx-dev mailing list > [email protected] <mailto:[email protected]> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
