[
https://issues.apache.org/jira/browse/OAK-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731590#comment-15731590
]
Francesco Mari commented on OAK-5017:
-------------------------------------
The latest group of problematic tests related to Cold Standby are the following.
{noformat}
FailoverIPRangeIT.testFailoverCorrectListIPv6UseIPv6:133->createTestWithConfig:164
expected:<{ root = { ... } }> but was:<{ root : { } }>
FailoverIPRangeIT.testFailoverCorrectListUseIPv6:126->createTestWithConfig:164
expected:<{ root = { ... } }> but was:<{ root : { } }>
FailoverIPRangeIT.testFailoverLocalClientUseIPv6:65->createTestWithConfig:164
expected:<{ root = { ... } }> but was:<{ root : { } }>
{noformat}
These tests always fail because the following error.
{noformat}
io.netty.channel.AbstractChannel$AnnotatedSocketException: Protocol family
unavailable: /0:0:0:0:0:0:0:1:50238
at sun.nio.ch.Net.connect0(Native Method) ~[na:1.8.0_102]
at sun.nio.ch.Net.connect(Net.java:454) ~[na:1.8.0_102]
at sun.nio.ch.Net.connect(Net.java:446) ~[na:1.8.0_102]
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
~[na:1.8.0_102]
at
io.netty.channel.socket.nio.NioSocketChannel.doConnect(NioSocketChannel.java:242)
~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
...
{noformat}
The test and the error hint that the issue might be related to the way IPv6 is
implemented in the JVM or configured on the host. The following table reports
the build, the node and the JVM where the tests failed.
{noformat}
1320
1319 beam2 (1.8) beam3 (1.8)
1318 beam3 (1.8) beam2 (1.8)
1317
1316 beam2 (1.8) beam3 (1.8)
1315
1314 beam1 (1.7)
1313
1312
1311
{noformat}
The following table reports the same information for every time the tests
passed.
{noformat}
1320 H18 (1.8) ubuntu-eu2 (1.8) H16 (1.8) H10 (1.8) H15 (1.7) H12 (1.7)
ubuntu-1 (1.7) proserpina-test (1.7)
1319 H18 (1.8) H16 (1.8) H15 (1.7) ubuntu-1 (1.7) H16 (1.7) proserpina-test
(1.7)
1318 H18 (1.8) H15 (1.8) ubuntu-1 (1.7) proserpina-test (1.7)
1317
1316 H18 (1.8) H16 (1.8) H15 (1.7) ubuntu-1 (1.7) proserpina-test (1.7)
1315
1314 ubuntu-6 (1.8) ubuntu-4 (1.8) ubuntu-2 (1.8) H10 (1.8) H12 (1.7) H17 (1.7)
H11 (1.7)
1313
1312
1311
{noformat}
The lack of overlapping between the node names hint that the problem might be
related to the configuration of the nodes grouped under the "beam" label.
> Standby test failures
> ---------------------
>
> Key: OAK-5017
> URL: https://issues.apache.org/jira/browse/OAK-5017
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Francesco Mari
> Labels: test-failure
> Fix For: 1.6, 1.5.15
>
>
> I've recently seen a couple of the standby tests fail. E.g. on Jenkins:
> https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1245/
> {noformat}
> java.lang.AssertionError: expected:
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... },
> root = { ... } }> but was:
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... },
> root = { ... } }>
> at
> org.apache.jackrabbit.oak.segment.standby.StandbyTestIT.testSyncLoop(StandbyTestIT.java:122)
> {noformat}
> {noformat}
> java.lang.AssertionError: expected:
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... },
> root = { ... } }> but was:
> org.apache.jackrabbit.oak.segment.SegmentNodeState<{ checkpoints = { ... },
> root = { ... } }>
> at
> org.apache.jackrabbit.oak.segment.standby.StandbyTestIT.testSyncLoop(StandbyTestIT.java:122)
> {noformat}
> {{org.apache.jackrabbit.oak.segment.standby.ExternalSharedStoreIT.testProxySkippedBytes}}:
> {noformat}
> java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { }
> }>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
