I believe this is where it is set
https://github.com/opendaylight/controller/blob/master/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/datastore/ShardDataTree.java#L106
Not sure if there is any way to configure it though any akka/cluster config
kn
Srini,
Looks like you have operational persistence on. It seems something must
have changed between the restart. Upgrade? Data model change?
Caused by: org.opendaylight.yangtools.yang.data.api.schema.tree.
ModifiedNodeDoesNotExistException: Node /(urn:ietf:params:xml:ns:yang:
ietf-network?revisi
Hi
We setup a cluster of 3 instances, and rebooted one of the instances.
During restart, it printed the following and went to a bad state where we
could not use the operational shard. Has anyone seen this akka exception
before? Is there any way to get out of this type of slate state?
2017-05-10
On Mon, May 15, 2017 at 5:06 PM, Satish Dutt wrote:
> Hi Michael,
>
>
>
> Thanks for your response. I am writing a custom cohort class for some
> validation purpose, which extends the DOMDataTreeCommitCohort of the
> mdsal.dom.api package and overrides the canCommit(). canCommit() in my
> cohort
Hi Michael,
Thanks for your response. I am writing a custom cohort class for some
validation purpose, which extends the DOMDataTreeCommitCohort of the
mdsal.dom.api package and overrides the canCommit(). canCommit() in my cohort
does some validations and just return a Future object indicating s
Satish,
On Mon, May 15, 2017 at 2:26 PM, Satish Dutt wrote:
> Hi,
>
>
>
> Is there any way to increase the timeout value for a commit operation to
> the datastore ? Sometimes I get timeout value during the commit operation
>
AFAIK, the 5s timeout you're experience below from a commit to the
dat
Hi,
Is there any way to increase the timeout value for a commit operation to the
datastore ? Sometimes I get timeout value during the commit operation
{
"errors": {
"error": [
{
"error-type": "application",
"error-tag": "operation-failed",
"error-message": "ca
