You also need to configure the seed-nodes to point to at least one of the
nodes in the cluster.
On Fri, Jun 30, 2017 at 8:14 AM, Tom Pantelis <tompante...@gmail.com> wrote:
> I don't know what you did but it looks like the DOMEntityOwnershipService
> didn't start. Look for other errors. To add a new node, start it up as
> single-node but with a different member name than the rest. It will have no
> shards created since the module-shards.conf defaults to member-1. Then use
> the RPC to add replicas for all shards.
>
> On Fri, Jun 30, 2017 at 8:00 AM, Venkatrangan G - ERS, HCL Tech <
> venkatrang...@hcl.com> wrote:
>
>> Hi Tom,
>>
>> Thanks for the response. Is there any procedure to use these rpc and add
>> a new ODL to an existing cluster.
>>
>> We tried without this rpc and ended up with blueprint errors in the new
>> ODL that we were trying to add. Can you please suggest.
>>
>>
>>
>> ------8ß--------------
>>
>>
>>
>> 1:07:20,050 | WARN | saction-32-34'}} | DeadlockMonitor
>> | 134 - org.opendaylight.controller.config-manager - 0.6.0.Carbon |
>> ModuleIdentifier{factoryName='runtime-generated-mapping',
>> instanceName='runtime-mapping-singleton'} did not finish after 209023 ms
>>
>> 2017-06-13 21:07:23,085 | ERROR | rint Extender: 3 |
>> BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core
>> - 1.6.1 | Unable to start blueprint container for bundle
>> org.opendaylight.mdsal.singleton-dom-impl/2.2.0.Carbon due to unresolved
>> dependencies [(objectClass=org.opendaylight.mdsal.eos.dom.api.
>> DOMEntityOwnershipService)]
>>
>> java.util.concurrent.TimeoutException
>>
>> at org.apache.aries.blueprint.con
>> tainer.BlueprintContainerImpl$1.run(BlueprintContainerImpl.
>> java:371)[15:org.apache.aries.blueprint.core:1.6.1]
>>
>> at org.apache.aries.blueprint.uti
>> ls.threading.impl.DiscardableRunnable.run(DiscardableRunnabl
>> e.java:48)[15:org.apache.aries.blueprint.core:1.6.1]
>>
>> at java.util.concurrent.Executors$RunnableAdapter.call(
>> Executors.java:511)[:1.8.0_45]
>>
>> at java.util.concurrent.FutureTas
>> k.run(FutureTask.java:266)[:1.8.0_45]
>>
>> at java.util.concurrent.Scheduled
>> ThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledT
>> hreadPoolExecutor.java:180)[:1.8.0_45]
>>
>> at java.util.concurrent.Scheduled
>> ThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPo
>> olExecutor.java:293)[:1.8.0_45]
>>
>> at java.util.concurrent.ThreadPoo
>> lExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_45]
>>
>> at java.util.concurrent.ThreadPoo
>> lExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_45]
>>
>> at java.lang.Thread.run(Thread.java:745)[:1.8.0_45]
>>
>> 2017-06-13 21:07:23,085 | ERROR | rint Extender: 2 |
>> BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core
>> - 1.6.1 | Unable to start blueprint container for bundle
>> org.opendaylight.mdsal.eos-binding-adapter/2.2.0.Carbon due to
>> unresolved dependencies [(objectClass=org.opendaylight
>> .mdsal.binding.dom.codec.api.BindingNormalizedNodeSerializer),
>> (objectClass=org.opendaylight.mdsal.eos.dom.api.DOMEntityOwn
>> ershipService)]
>>
>> java.util.concurrent.TimeoutException
>>
>> at org.apache.aries.blueprint.con
>> tainer.BlueprintContainerImpl$1.run(BlueprintContainerImpl.
>> java:371)[15:org.apache.aries.blueprint.core:1.6.1]
>>
>> at org.apache.aries.blueprint.uti
>> ls.threading.impl.DiscardableRunnable.run(DiscardableRunnabl
>> e.java:48)[15:org.apache.aries.blueprint.core:1.6.1]
>>
>> at java.util.concurrent.Executors$RunnableAdapter.call(
>> Executors.java:511)[:1.8.0_45]
>>
>> at java.util.concurrent.FutureTas
>> k.run(FutureTask.java:266)[:1.8.0_45]
>>
>> at java.util.concurrent.Scheduled
>> ThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledT
>> hreadPoolExecutor.java:180)[:1.8.0_45]
>>
>> at java.util.concurrent.Scheduled
>> ThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPo
>> olExecutor.java:293)[:1.8.0_45]
>>
>> at java.util.concurrent.ThreadPoo
>> lExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_45]
>>
>> at java.util.concurrent.ThreadPoo
>> lExecutor$Worker.run(ThreadPoolExecu
>>
>> --------------------8ß--------------------
>>
>>
>>
>>
>>
>> Regards,
>>
>> Venkat G
>>
>>
>>
>> *From:* Tom Pantelis [mailto:tompante...@gmail.com]
>> *Sent:* 15 June 2017 03:40
>> *To:* Venkatrangan G - ERS, HCL Tech <venkatrang...@hcl.com>
>> *Cc:* controller-dev@lists.opendaylight.org; Hari Prasad <hari...@hcl.com>;
>> Balakrishnan Karuppasamy <balakrishnan...@hcl.com>
>> *Subject:* Re: [controller-dev] Add new ODL node to a cluster
>>
>>
>>
>> Venkat,
>>
>>
>>
>> There are RPCs defined in https://github.com/opendayl
>> ight/controller/blob/master/opendaylight/md-sal/sal-
>> cluster-admin-api/src/main/yang/cluster-admin.yang for dynamically
>> adding shard replicas to an existing cluster.
>>
>>
>>
>> Tom
>>
>>
>>
>> On Wed, Jun 14, 2017 at 4:22 PM, Venkatrangan G - ERS, HCL Tech <
>> venkatrang...@hcl.com> wrote:
>>
>> Hi,
>>
>>
>>
>> Is there any documented procedure to add more nodes to the ODL cluster.
>> We are looking at adding 2 nodes to an existing 3node cluster without
>> bringing the nodes down. Is there any procedure documented for the same?
>> Can you please guide us.
>>
>>
>>
>>
>>
>> Regards,
>>
>> Venkat G
>>
>>
>>
>> ::DISCLAIMER::
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> ----------------------------
>>
>> The contents of this e-mail and any attachment(s) are confidential and
>> intended for the named recipient(s) only.
>> E-mail transmission is not guaranteed to be secure or error-free as
>> information could be intercepted, corrupted,
>> lost, destroyed, arrive late or incomplete, or may contain viruses in
>> transmission. The e mail and its contents
>> (with or without referred errors) shall therefore not attach any
>> liability on the originator or HCL or its affiliates.
>> Views or opinions, if any, presented in this email are solely those of
>> the author and may not necessarily reflect the
>> views or opinions of HCL or its affiliates. Any form of reproduction,
>> dissemination, copying, disclosure, modification,
>> distribution and / or publication of this message without the prior
>> written consent of authorized representative of
>> HCL is strictly prohibited. If you have received this email in error
>> please delete it and notify the sender immediately.
>> Before opening any email and/or attachments, please check them for
>> viruses and other defects.
>>
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> ----------------------------
>>
>>
>> _______________________________________________
>> controller-dev mailing list
>> controller-dev@lists.opendaylight.org
>> https://lists.opendaylight.org/mailman/listinfo/controller-dev
>>
>>
>>
>
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
