These are chat archives for atomix/atomix
We are no longer monitoring this channel, please join Slack! https://join.slack.com/t/atomixio/shared_invite/enQtNDgzNjA5MjMyMDUxLTVmMThjZDcxZDE3ZmU4ZGYwZTc2MGJiYjVjMjFkOWMyNmVjYTc5YjExYTZiOWFjODlkYmE2MjNjYzZhNjU2MjY
df -h Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/disk1 112Gi 60Gi 51Gi 54% 15861002 13462260 54% /
AppendRequests are failing
AppendRequest to /192.168.123.1:9876 failed. Reason: io.atomix.catalyst.transport.TransportException: java.util.concurrent.CompletionException: org.onosproject.store.cluster.messaging.MessagingException$NoRemoteHandler: No remote message handler registered for this message
AppendRequestfailures were a part of normal operation during startup
So, @jhall11 I don't really know what else I can do to debug this right now. It's working fine when I run it with
But for good measure, I also just rewrote the entire Copycat transport myself:
I know that branch has a correct implementation of Copycat's transport. And again, it seems to be running well on a three node cluster with
onos.py. I logged into the ONOS shell and enabled DEBUG logging for Copycat and watched the command/query request/response logs fly by. I also compared the logs to
master for good measure and the behavior was essentially the same. That said, it doesn’t seem like the bug I fixed last night should have even been causing the dismall communication issues that are showing up in your logs. Obvious,y I’m still new at this and figuring everything out. So what am I missing?
CloseConnectionmessage via the existing interface - if all else fails. If that doesn't work then there's something else going on.