Re: [controller-dev] [netconf-dev] Validation hooks when using restconf

2017-03-20 Thread Satish Dutt 
Thanks Tomas

From: Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at Cisco) 
[mailto:tc...@cisco.com]
Sent: Monday, March 20, 2017 8:58 PM
To: Satish Dutt ; controller-dev@lists.opendaylight.org; 
controller-us...@lists.opendaylight.org; netconf-...@lists.opendaylight.org
Subject: RE: [netconf-dev] Validation hooks when using restconf

This should be possible by leveraging the DOMDataTreeCommitCohort api's.

https://github.com/opendaylight/mdsal/blob/454903c516e9405ff4a1af6392a31b00c04852fa/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeCommitCohort.java

https://github.com/opendaylight/mdsal/blob/596b89ec503f56c87d066c00d6550e675eb7cf0c/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeCommitCohortRegistry.java

Tomas

From: 
netconf-dev-boun...@lists.opendaylight.org
 [mailto:netconf-dev-boun...@lists.opendaylight.org] On Behalf Of Satish Dutt
Sent: Sunday, March 19, 2017 16:07
To: 
controller-dev@lists.opendaylight.org;
 
controller-us...@lists.opendaylight.org;
 netconf-...@lists.opendaylight.org
Subject: [netconf-dev] Validation hooks when using restconf

Hi,

>From the northbound applications we are using the restconf APIs to push the 
>JSON data to the ODL controller. Is there any programming hooks through which 
>the JSON data can be validated in the controller before allowing the data to 
>be stored in the configuration datastore ?

Regards
Satish
___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Re: [controller-dev] prevLogIndex 3 was found in the log but the term -1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4

2017-03-20 Thread Muthukumaran K 
@Guy,

URL should be

http://:8181/jolokia/read/org.opendaylight.controller:Category=Shards,name=member--shard-topology-operational,type=DistributedOperationalDatastore

Regards
Muthu



From: controller-dev-boun...@lists.opendaylight.org 
[mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Sela, Guy
Sent: Monday, March 20, 2017 7:24 PM
To: Tom Pantelis 
Cc: odl netvirt dev ; 
controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] prevLogIndex 3 was found in the log but the term 
-1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, 
snapshotIndex: 4

https://bugs.opendaylight.org/show_bug.cgi?id=8022

The dump from  
http://:8181/jolokia/read/org.opendaylight.controller:Category=Shards,name=member--shard-topology-operational,type=DistributedOperDatastore didn’t work for me.
So I only added the logs with TRACE on SHARDs.


From: Tom Pantelis [mailto:tompante...@gmail.com]
Sent: Monday, March 20, 2017 2:41 PM
To: Sela, Guy >
Cc: 
controller-dev@lists.opendaylight.org;
 odl netvirt dev 
>
Subject: Re: [controller-dev] prevLogIndex 3 was found in the log but the term 
-1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, 
snapshotIndex: 4

Actually set the log level to trace instead of debug.

On Mon, Mar 20, 2017 at 8:29 AM, Tom Pantelis 
> wrote:
Hmm... please enable Shard debug (add 
log4j.logger.org.opendaylight.controller.cluster.datastore.Shard=debug to 
etc/org.ops4j.pax.logging.cfg) on all 3 nodes and let it run for like 10 sec 
and capture the logs and open a bug. Also capture the JMX Shard output from 
each node, ie:

   
http://:8181/jolokia/read/org.opendaylight.controller:Category=Shards,name=member--shard-topology-operational,type=DistributedOperDatastore

replacing  appropriately for each node.

Please provide the steps that led up to it, eg were nodes restarted etc

On Mon, Mar 20, 2017 at 7:50 AM, Sela, Guy 
> wrote:
Latest code in a 3-node cluster, and I’m seeing the following errors while OVSs 
are connecting to the ODL.

2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]

Re: [controller-dev] How to conveniently deploy odl cluster

2017-03-20 Thread bjb 


Hello Alexis：
In the docker deploy, are three dockers deployed on the same linux server? 
If so, how to deal with the openflow port 6633? Each controller must expose 
port 6633.
if not on the same linux server? How to distribute three dockers on each 
linux server. Will you use kubernetes or anything else.


Hope to get your help.
Thanks



At 2017-02-23 03:27:33, "Alexis de Talhouët"  wrote:





2017-02-22 6:25 GMT-05:00 bjb :

Hello All:
   
I see the steps to deploy a cluster in 
http://docs.opendaylight.org/en/latest/getting-started-guide/common-features/clustering.html?highlight=clustering

I need to modify *.conf(akka.conf, modules.conf, module-shards.conf) on 
each cluster member and then start karaf. For convenience, configure_cluster.sh 
is provided to automatic generate *.conf in configuration/initial. But it also 
need to deploy on each cluster member. When the cluster members are huge, e.g 
32 members form a cluster, the depoly will be inconvenient.


AdT: Checkout this setup that was merge recently in packaging repo: 
https://github.com/opendaylight/integration-packaging/tree/master/tutorials/cluster-nodes

It could help achieve what you're seeking, to some extend. Basically, configure 
your cluster once, and delpoy it once and for all.

 

Is there any other plans for easily deploying? I thinked two ways to depoly 
a cluster, is it feasible?
1) Add a new feature in odl to manage cluster, it includes "create cluster" 
"destroy cluster" "dynamic add member" and so on. All the controllers start 
karaf in standalone mode without cluster configuration. We just need to send 
request to one cluster member, the member transfer configuration to akka.conf 
module-shard.conf, clean old journal and snapshots. Then the member send 
request to all the other cluster members. The other members do the same thing, 
after that, all members restart karaf to apply cluster configuration. In this 
way, user add easily do cluster management. 

2) If odl will not support dynamic add or remove cluster member, deploying 
cluster in advance will be less difficult. We can use some depoly tools like 
ansible to distribute *.conf on all cluster members.
  
Hope to get your help.
Thanks




 





 





 


___
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

Re: [controller-dev] [netconf-dev] Validation hooks when using restconf

2017-03-20 Thread Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at Cisco) 
This should be possible by leveraging the DOMDataTreeCommitCohort api's.

https://github.com/opendaylight/mdsal/blob/454903c516e9405ff4a1af6392a31b00c04852fa/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeCommitCohort.java

https://github.com/opendaylight/mdsal/blob/596b89ec503f56c87d066c00d6550e675eb7cf0c/dom/mdsal-dom-api/src/main/java/org/opendaylight/mdsal/dom/api/DOMDataTreeCommitCohortRegistry.java

Tomas

From: netconf-dev-boun...@lists.opendaylight.org 
[mailto:netconf-dev-boun...@lists.opendaylight.org] On Behalf Of Satish Dutt
Sent: Sunday, March 19, 2017 16:07
To: controller-dev@lists.opendaylight.org; 
controller-us...@lists.opendaylight.org; netconf-...@lists.opendaylight.org
Subject: [netconf-dev] Validation hooks when using restconf

Hi,

>From the northbound applications we are using the restconf APIs to push the 
>JSON data to the ODL controller. Is there any programming hooks through which 
>the JSON data can be validated in the controller before allowing the data to 
>be stored in the configuration datastore ?

Regards
Satish
___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Re: [controller-dev] prevLogIndex 3 was found in the log but the term -1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4

2017-03-20 Thread Sela, Guy 
https://bugs.opendaylight.org/show_bug.cgi?id=8022

The dump from  
http://:8181/jolokia/read/org.opendaylight.controller:Category=Shards,name=member--shard-topology-operational,type=DistributedOperDatastore didn’t work for me.
So I only added the logs with TRACE on SHARDs.


From: Tom Pantelis [mailto:tompante...@gmail.com]
Sent: Monday, March 20, 2017 2:41 PM
To: Sela, Guy 
Cc: controller-dev@lists.opendaylight.org; odl netvirt dev 

Subject: Re: [controller-dev] prevLogIndex 3 was found in the log but the term 
-1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, 
snapshotIndex: 4

Actually set the log level to trace instead of debug.

On Mon, Mar 20, 2017 at 8:29 AM, Tom Pantelis 
> wrote:
Hmm... please enable Shard debug (add 
log4j.logger.org.opendaylight.controller.cluster.datastore.Shard=debug to 
etc/org.ops4j.pax.logging.cfg) on all 3 nodes and let it run for like 10 sec 
and capture the logs and open a bug. Also capture the JMX Shard output from 
each node, ie:

   
http://:8181/jolokia/read/org.opendaylight.controller:Category=Shards,name=member--shard-topology-operational,type=DistributedOperDatastore

replacing  appropriately for each node.

Please provide the steps that led up to it, eg were nodes restarted etc

On Mon, Mar 20, 2017 at 7:50 AM, Sela, Guy 
> wrote:
Latest code in a 3-node cluster, and I’m seeing the following errors while OVSs 
are connecting to the ODL.

2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - 
org.opendaylight.controller.sal-clustering-commons
 - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false,

Re: [controller-dev] prevLogIndex 3 was found in the log but the term -1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4

2017-03-20 Thread Tom Pantelis 
Actually set the log level to trace instead of debug.

On Mon, Mar 20, 2017 at 8:29 AM, Tom Pantelis  wrote:

> Hmm... please enable Shard debug (add log4j.logger.org.opendaylight.
> controller.cluster.datastore.Shard=debug to
> etc/org.ops4j.pax.logging.cfg) on all 3 nodes and let it run for like 10
> sec and capture the logs and open a bug. Also capture the JMX Shard
> output from each node, ie:
>
>http:// :8181/jolokia/read/org.opendaylight.
> controller:Category=Shards,name=member-**-shard-topology-
> operational,type=DistributedOperDatastore
>
> replacing ** appropriately for each node.
>
> Please provide the steps that led up to it, eg were nodes restarted etc
>
> On Mon, Mar 20, 2017 at 7:50 AM, Sela, Guy  wrote:
>
>> Latest code in a 3-node cluster, and I’m seeing the following errors
>> while OVSs are connecting to the ODL.
>>
>>
>>
>> 2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
>> prevLogIndex 3 was found in the log but the term -1 is not equal to the
>> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>>
>> 2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
>> Follower is out-of-sync so sending negative reply: AppendEntriesReply
>> [term=1, success=false, followerId=member-3-shard-topology-operational,
>> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
>> payloadVersion=5, raftVersion=3]
>>
>> 2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
>> prevLogIndex 3 was found in the log but the term -1 is not equal to the
>> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>>
>> 2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
>> Follower is out-of-sync so sending negative reply: AppendEntriesReply
>> [term=1, success=false, followerId=member-3-shard-topology-operational,
>> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
>> payloadVersion=5, raftVersion=3]
>>
>> 2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
>> prevLogIndex 3 was found in the log but the term -1 is not equal to the
>> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>>
>> 2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
>> Follower is out-of-sync so sending negative reply: AppendEntriesReply
>> [term=1, success=false, followerId=member-3-shard-topology-operational,
>> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
>> payloadVersion=5, raftVersion=3]
>>
>> 2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
>> prevLogIndex 3 was found in the log but the term -1 is not equal to the
>> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>>
>> 2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
>> Follower is out-of-sync so sending negative reply: AppendEntriesReply
>> [term=1, success=false, followerId=member-3-shard-topology-operational,
>> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
>> payloadVersion=5, raftVersion=3]
>>
>> 2017-03-20 13:48:38,180 | INFO  | lt-dispatcher-68 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
>> prevLogIndex 3 was found in the log but the term -1 is not equal to the
>> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>>
>> 2017-03-20 13:48:38,180 | INFO  | lt-dispatcher-68 |
>> Shard| 207 - 
>> org.opendaylight.controller.sal-clustering-commons
>> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
>> Follower is out-of-sync so sending negative reply: AppendEntriesReply
>> [term=1, success=false,

Re: [controller-dev] prevLogIndex 3 was found in the log but the term -1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4

2017-03-20 Thread Tom Pantelis 
Hmm... please enable Shard debug (add
log4j.logger.org.opendaylight.controller.cluster.datastore.Shard=debug to
etc/org.ops4j.pax.logging.cfg) on all 3 nodes and let it run for like 10
sec and capture the logs and open a bug. Also capture the JMX Shard output
from each node, ie:

   http:// 
:8181/jolokia/read/org.opendaylight.controller:Category=Shards,name=member-**-shard-topology-operational,type=DistributedOperDatastore

replacing ** appropriately for each node.

Please provide the steps that led up to it, eg were nodes restarted etc

On Mon, Mar 20, 2017 at 7:50 AM, Sela, Guy  wrote:

> Latest code in a 3-node cluster, and I’m seeing the following errors while
> OVSs are connecting to the ODL.
>
>
>
> 2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
> prevLogIndex 3 was found in the log but the term -1 is not equal to the
> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>
> 2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
> Follower is out-of-sync so sending negative reply: AppendEntriesReply
> [term=1, success=false, followerId=member-3-shard-topology-operational,
> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
> payloadVersion=5, raftVersion=3]
>
> 2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
> prevLogIndex 3 was found in the log but the term -1 is not equal to the
> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>
> 2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
> Follower is out-of-sync so sending negative reply: AppendEntriesReply
> [term=1, success=false, followerId=member-3-shard-topology-operational,
> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
> payloadVersion=5, raftVersion=3]
>
> 2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
> prevLogIndex 3 was found in the log but the term -1 is not equal to the
> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>
> 2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
> Follower is out-of-sync so sending negative reply: AppendEntriesReply
> [term=1, success=false, followerId=member-3-shard-topology-operational,
> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
> payloadVersion=5, raftVersion=3]
>
> 2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
> prevLogIndex 3 was found in the log but the term -1 is not equal to the
> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>
> 2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
> Follower is out-of-sync so sending negative reply: AppendEntriesReply
> [term=1, success=false, followerId=member-3-shard-topology-operational,
> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
> payloadVersion=5, raftVersion=3]
>
> 2017-03-20 13:48:38,180 | INFO  | lt-dispatcher-68 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The
> prevLogIndex 3 was found in the log but the term -1 is not equal to the
> append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
>
> 2017-03-20 13:48:38,180 | INFO  | lt-dispatcher-68 |
> Shard| 207 - 
> org.opendaylight.controller.sal-clustering-commons
> - 1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower):
> Follower is out-of-sync so sending negative reply: AppendEntriesReply
> [term=1, success=false, followerId=member-3-shard-topology-operational,
> logLastIndex=5, logLastTerm=1, forceInstallSnapshot=false,
> payloadVersion=5, raftVersion=3]
>
>
>
> Thanks,
>
> Guy Sela
>
>
>
> ___
> controller-dev mailing list
>

[controller-dev] prevLogIndex 3 was found in the log but the term -1 is not equal to the append entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4

2017-03-20 Thread Sela, Guy 
Latest code in a 3-node cluster, and I'm seeing the following errors while OVSs 
are connecting to the ODL.

2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:36,101 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:36,621 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:37,140 | INFO  | lt-dispatcher-29 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:37,661 | INFO  | lt-dispatcher-51 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]
2017-03-20 13:48:38,180 | INFO  | lt-dispatcher-68 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): The 
prevLogIndex 3 was found in the log but the term -1 is not equal to the append 
entriesprevLogTerm 1 - lastIndex: 5, snapshotIndex: 4
2017-03-20 13:48:38,180 | INFO  | lt-dispatcher-68 | Shard  
  | 207 - org.opendaylight.controller.sal-clustering-commons - 
1.5.0.SNAPSHOT | member-3-shard-topology-operational (Follower): Follower is 
out-of-sync so sending negative reply: AppendEntriesReply [term=1, 
success=false, followerId=member-3-shard-topology-operational, logLastIndex=5, 
logLastTerm=1, forceInstallSnapshot=false, payloadVersion=5, raftVersion=3]

Thanks,
Guy Sela

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev