Results 1 to 4 of 4

Thread: MongodbRetention on distributed architecture

  1. #1

    MongodbRetention on distributed architecture

    Hello everyone, hello nap,

    First of all, there goes my configuration:
    I have two realms, each have their scheduler, obviously. Each scheduler has a spare as well, in case of failure.
    I have two mongodbretention modules, one for each realm.

    In order to maintain retention, in case of failure, in the mongodbretention modules definition, do you I have to put the ip of master and spare of mongod or just one and let mongod replicate itself with mongod options ?
    I havent seen it clearly mentionned that shinken does the work in this case.

    I hope I am understandable ;D

    Thanks,
    David

  2. #2
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: MongodbRetention on distributed architecture

    I don't know, can you look at mongodb documentation? If I'm not wrong the URI for connexion is based on both IPS.
    No direct support by personal message. Please open a thread so everyone can see the solution

  3. #3

    Re: MongodbRetention on distributed architecture

    Did not see anything on the mongodb doc related to shinken.
    I will test the behaviour tonight on virtual machines and keep you up to date

    David

  4. #4
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: MongodbRetention on distributed architecture

    Of course you won't find shinken in mongodb

    I was talking about generic URI for mongo
    No direct support by personal message. Please open a thread so everyone can see the solution

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •