2 Replies Latest reply on Mar 9, 2016 1:33 PM by Wolfgang Kamradek

    Inheriting configs from domain controller and start nodes without domain controller?

    Wolfgang Kamradek Newbie

      Hello,

       

      I am new to this forum, and I am not a Java developer, so please forgive me if the answer to my question is too obvious.

      My question is concerning a Firefly Domain-Controller Setup which I currently try to create in my test environment.

      I configured everything needed for my Firefly instances on the domain controller in the domain.xml on the domain controller, e.g. "Xmx" as max-size="1024m".

      As expected the 2 Firefly nodes are inheriting these settings from the domain controller. But: As soon as the domain controller

      is down, the nodes are unable to start, arguing that they can not connect to the domain controller.

       

      My question is: Is it possible that the nodes are able to start without the presence of the domain controller? If so, the nodes need to know and store their configuration (e.g. max-size="1024m") locally. How could I accomplish that the nodes inherit the configuration from domain controller at first start *and store the configuration locally*, so they are able to start without the domain controller?

       

      Otherwise - lets assume I try to configure a HA szenario. Do I need a redundant domain-controller to make sure the nodes are bootable in case one of the domain controller is unavailable?


      Thanks for your insights.


      \\'.

        • 1. Re: Inheriting configs from domain controller and start nodes without domain controller?
          Jay SenSharma Master

          domain.sh script has an option "--cached-dc " ,  I guess you are looking out for the same.  This option can be used to boot HC even when DC is down (with all the caveats above).

           

          --cached-dc                         If this host is not the Domain

                                                  Controller and cannot contact the

                                                  Domain Controller at boot, boot using a

                                                  locally cached copy of the domain

                                                  configuration (see --backup)

           

          --backup                            Keep a copy of the persistent domain

                                                  configuration even if this host is not

                                                  the Domain Controller

           

                         --backup tells the host-controller to backup the model locally. --cached-dc to not connect to the remote domain-controller and use the locally cached model instead.

           

          Regards

          Jay SenSharma

          • 2. Re: Inheriting configs from domain controller and start nodes without domain controller?
            Wolfgang Kamradek Newbie

            OK - thanks a lot - that was exactly what I was searching for.