These are chat archives for atomix/atomix

6th
Aug 2018
Junbo Ruan
@aruanruan
Aug 06 2018 03:44
@kuujo nothing more valuable
is there easy way to create atomix client?
i build a cluster in remote vm
i need create client in local machine to access the cluster
Johno Crawford
@johnou
Aug 06 2018 05:16
@aruanruan might be valuable if you can reproduce it with trace logging enabled
Junbo Ruan
@aruanruan
Aug 06 2018 05:28
@johnou ok, i will try
@johnou is there an easy way to create atomix client?
Johno Crawford
@johnou
Aug 06 2018 05:30
use the agent?
Junbo Ruan
@aruanruan
Aug 06 2018 05:30
yes
Johno Crawford
@johnou
Aug 06 2018 05:31
that's my answer
depends what you want to do with the agent
Junbo Ruan
@aruanruan
Aug 06 2018 05:31
i am puzzled
Johno Crawford
@johnou
Aug 06 2018 05:41
well let's say you started two nodes on your remote vm
you could start a client with a config like this
cluster {
  name: atomix
  discovery {
    type: bootstrap
    nodes.1 {
      id: atomix-1
      address: "remoteiporhost:5679"
    }
    nodes.2 {
      id: atomix-2
      address: "remoteiporhost:5680"
    }
  }
}
Junbo Ruan
@aruanruan
Aug 06 2018 06:12
protected static AtomixBuilder buildAtomix(Map<String, String> addresses) {
        Collection<Node> nodes = new ArrayList<>();

        addresses.forEach((id, address) -> {
            Node node = Node.builder().withId(String.valueOf(id)).withAddress(Address.from(address)).build();
            nodes.add(node);
        });

        ClusterConfig clusterConfig = new ClusterConfig(); 
        clusterConfig.setClusterId("atomix");
        MemberConfig memberConfig = new MemberConfig();
        memberConfig.setAddress(Address.local());
        clusterConfig.setNodeConfig(memberConfig);
        AtomixConfig config = new AtomixConfig();
        config.setClusterConfig(clusterConfig);

        return Atomix.builder(config).withMembershipProvider(new BootstrapDiscoveryProvider(nodes));
}
Junbo Ruan
@aruanruan
Aug 06 2018 06:57

i implements a timeout strategy to change node state in my service
client use raft protocol

@Override
      protected ProxyProtocol protocol() {
        return MultiRaftProtocol.builder()
            .withMaxRetries(5)
            .build();
      }

log shows, create timer in 2018-08-06 14:52:47, timer will expired in 10 seconds

2018-08-06 14:52:47,525 INFO (DefaultUdoGraphService.java:256)- create timer for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-0 with 10 seconds
2018-08-06 14:52:47,541 INFO (DefaultUdoGraphService.java:256)- create timer for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-1 with 10 seconds
2018-08-06 14:52:47,541 INFO (DefaultUdoGraphService.java:256)- create timer for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-2 with 10 seconds
2018-08-06 14:52:47,541 INFO (DefaultUdoGraphService.java:256)- create timer for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-3 with 10 seconds
2018-08-06 14:52:47,541 INFO (DefaultUdoGraphService.java:256)- create timer for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-4 with 10 seconds
2018-08-06 14:52:47,541 INFO (DefaultUdoGraphService.java:256)- create timer for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-5 with 10 seconds

but timer executed at 2018-08-06 14:53:15,044

2018-08-06 14:53:15,044 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-2
2018-08-06 14:53:15,044 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-2
2018-08-06 14:53:15,044 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-4
2018-08-06 14:53:15,044 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-4
2018-08-06 14:53:15,044 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-6
2018-08-06 14:53:15,044 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-6
2018-08-06 14:53:15,059 INFO (DefaultUdoGraphService.java:571)- timeout for: 3d3b08c7-b9fc-4f45-897b-71828b1b0230-8

it is about 20 seconds

Junbo Ruan
@aruanruan
Aug 06 2018 07:08

if i use multiPrimary protocal

@Override
    protected ProxyProtocol protocol() {
        return MultiPrimaryProtocol.builder().withBackups(2).withMaxRetries(5).build();
    }

timer create at 2018-08-06 15:06:32,

2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-0 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-1 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-2 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-3 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-4 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-5 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-6 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-7 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-8 with 10 seconds
2018-08-06 15:06:32,875 INFO (DefaultUdoGraphService.java:256)- create timer for: dcd8eb66-7926-44b9-b06a-348a36c015d3-9 with 10 seconds

timer expired at 2018-08-06 15:06:43, about 10 seconds

2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-2
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-4
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-6
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-8
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-9
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-7
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-5
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-3
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-1
2018-08-06 15:06:43,126 INFO (DefaultUdoGraphService.java:571)- timeout for: dcd8eb66-7926-44b9-b06a-348a36c015d3-0
Jordan Halterman
@kuujo
Aug 06 2018 17:23
@aruanruan what constitutes a timer? How are you creating a timer?
you created a timer primitive?
You can’t rely on primitive services for accurate clocks. Their only (and most important) guarantee is that the clocks are deterministic, and any relationship to wall clock time is merely approximated. The clock progresses when clients send keep-alives or write operations to the Raft partitions, which means if a client is sending a keep-alive every 20 seconds and is not operating on any other primitives in a partition, the deterministic wall clock will only progress every ~20 seconds.
Decrease the session timeout to get more frequent keel-alives from clients
All you can really say about Raft clocks is that the timeout will occur some time at or after the given Duration
Jordan Halterman
@kuujo
Aug 06 2018 17:48
And yes, if you want a client just create a node that doesn’t have any partition groups configured.
Jordan Halterman
@kuujo
Aug 06 2018 19:01
FYI I’m working with QA on bugs now so pretty much consider the code frozen. I doubt we’ll do anything else before 3.0.0
Jordan Halterman
@kuujo
Aug 06 2018 19:33
Expect ever more frequent release candidates. We’re going to try to get an ONOS release candidate done next week. Maybe will do an Atomix 3.0.0 release then. Depends on how irritated our QA team is with me at the time :-)
Johno Crawford
@johnou
Aug 06 2018 21:53
Don't forget the Netty update, should be this week fingers crossed
Junbo Ruan
@aruanruan
Aug 06 2018 23:33
morning, guys
i designed none service registering & finding system, when some time expired without 'touching' , the entry of service will change the status to 'dead'
yesterday , i met another puzzled testing
i started a cluster with 3 node
cluster {
    node {
        id: member1
        address: "10.93.85.253:5000"
    }
    discovery {
        type: bootstrap
        nodes.1: {
           id: member1
           address: "10.93.85.253:5000"
        }
        nodes.2: {
           id: member2
           address: "10.93.76.228:5000"
        }
        nodes.3: {
           id: member3
           address: "10.93.79.103:5000"
        }
    }
}

management-group {
  type: raft
  name: system
  partitions: 1
  storage-level: DISK
  members: [member1, member2, member3]
}

partition-groups.raft {
  type: raft
  name: raft
  partitions: 3
  storage-level: DISK
  members: [member1, member2, member3]
}


partition-groups.data {
  type: primary-backup
  name: data
  partitions: 7
}
starting the Agents
#!/bin/bash

pwd=`pwd`
echo $pwd
CLASSPATH=$pwd/lib/*:$pwd/*:$CLASSPATH

version=`java -version 2>&1 | head -1`
match=version
if [[ $version =~ $match ]]
then
    echo "java installed"
else
    echo "Error: java is not installed"
    exit 1
fi

JAVA=$JAVA_HOME/bin/java

nohup $JAVA -cp .:$CLASSPATH io.atomix.agent.AtomixAgent -c atomix2.conf --http-port 8080  $* 2>&1 >/dev/null &
#$JAVA -cp .:$CLASSPATH io.atomix.agent.AtomixAgent -c atomix1.conf --http-port 8080
Junbo Ruan
@aruanruan
Aug 06 2018 23:39
then a put & get data for testing the cluster
then i shutdowned each node by scrpt
#!/bin/bash
ps -ef |grep AtomixAgent | grep -v grep |awk '{print $2}'| xargs kill -9
when i restart the cluster, it doesn't work any more
some logs were:
log in 10.95.85.254 at 18:42:00
18:42:00.000 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.000 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.000 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [netty-messaging-event-epoll-client-3] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type raft-partition-1-append from 10.93.76.228:5000
18:42:00.000 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.001 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.001 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.002 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.002 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.002 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.002 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.002 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.002 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.003 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.003 [netty-messaging-event-epoll-client-2] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.003 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.85.253:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
logs in 10.93.76.228
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.76.228:5000 - Received message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.000 [netty-messaging-event-epoll-client-5] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.76.228:5000 - Received message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{492}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Received PublishRequest{session=492, eventIndex=529, previousIndex=528, events=[PrimitiveEvent{type=change, value=byte[]{length=93, hash=2116004929}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=-1057509305}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=328773}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=2145934773}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-208666895}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1043473289}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1281549453}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=308207225}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1653367433}}]}
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{492}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Inconsistent event index: 528
18:42:00.000 [netty-messaging-event-epoll-client-15] DEBUG i.a.c.m.impl.NettyMessagingService - Received a reply for message id:[1217274] but was unable to locate the request handle
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{492}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Sending ResetRequest{session=492, index=513}
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.76.228:5000 - Received message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.000 [netty-messaging-event-epoll-client-5] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.76.228:5000 - Received message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{492}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Received PublishRequest{session=492, eventIndex=529, previousIndex=528, events=[PrimitiveEvent{type=change, value=byte[]{length=93, hash=2116004929}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=-1057509305}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=328773}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=2145934773}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-208666895}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1043473289}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1281549453}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=308207225}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1653367433}}]}
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{492}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Inconsistent event index: 528
18:42:00.000 [raft-client-system-partition-1-8] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{492}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Sending ResetRequest{session=492, index=513}
18:42:00.000 [netty-messaging-event-epoll-client-0] DEBUG i.a.c.m.impl.NettyMessagingService - Received a reply for message id:[1217276] but was unable to locate the request handle
18:42:00.001 [raft-client-system-partition-1-8] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.76.228:5000 - Received message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.001 [netty-messaging-event-epoll-client-0] DEBUG i.a.c.m.impl.Netty
logs in 10.93.79.103
18:42:00.000 [raft-client-system-partition-1-13] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.79.103:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [raft-client-system-partition-1-13] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{503}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Received PublishRequest{session=503, eventIndex=529, previousIndex=528, events=[PrimitiveEvent{type=change, value=byte[]{length=93, hash=2116004929}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=-1057509305}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=328773}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=1752907763}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-208666895}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1043473289}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1281549453}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=308207225}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1653367433}}]}
18:42:00.000 [netty-messaging-event-epoll-client-14] DEBUG i.a.c.m.impl.NettyMessagingService - Received a reply for message id:[1226997] but was unable to locate the request handle
18:42:00.000 [raft-client-system-partition-1-13] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{503}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Inconsistent event index: 528
18:42:00.000 [raft-client-system-partition-1-13] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{503}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Sending ResetRequest{session=503, index=513}
18:42:00.000 [raft-client-system-partition-1-13] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.79.103:5000 - No handler for message type system-partition-1-reset-503 from 10.93.79.103:5000
18:42:00.000 [netty-messaging-event-epoll-client-14] DEBUG i.a.c.m.impl.NettyMessagingService - Received a reply for message id:[1227000] but was unable to locate the request handle
18:42:00.000 [netty-messaging-event-epoll-client-8] DEBUG i.a.c.m.impl.NettyMessagingService - 10.93.79.103:5000 - No handler for message type system-partition-1-reset-492 from 10.93.76.228:5000
18:42:00.000 [raft-client-system-partition-1-13] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{503}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Received PublishRequest{session=503, eventIndex=529, previousIndex=528, events=[PrimitiveEvent{type=change, value=byte[]{length=93, hash=2116004929}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=-1057509305}}, PrimitiveEvent{type=change, value=byte[]{length=93, hash=328773}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=1752907763}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-208666895}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1043473289}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1281549453}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=308207225}}, PrimitiveEvent{type=change, value=byte[]{length=73, hash=-1653367433}}]}
18:42:00.000 [netty-messaging-event-epoll-client-6] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.79.103:5000 - Received message type system-partition-1-publish-503 from 10.93.76.228:5000
18:42:00.000 [raft-client-system-partition-1-13] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{503}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Inconsistent event index: 528
18:42:00.000 [raft-client-system-partition-1-13] TRACE i.a.p.r.s.impl.RaftSessionListener - SessionClient{503}{type=PrimaryElectorType{name=PRIMARY_ELECTOR}, name=atomix-primary-elector} - Sending ResetRequest{session=503, index=513}
18:42:00.000 [netty-messaging-event-epoll-client-6] TRACE i.a.c.m.impl.NettyMessagingService - 10.93.79.103:5000 - Received message type system-partition-1-publish-503 from 10.93.76.228:5000
Junbo Ruan
@aruanruan
Aug 06 2018 23:44
logs were repeating almost same
image.png
the vm of 10.93.76.228