You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/07/19 16:12:00 UTC

[jira] [Commented] (OAK-9499) PersistentRedisCacheTest: Test failures

    [ https://issues.apache.org/jira/browse/OAK-9499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383430#comment-17383430 ] 

Konrad Windszus commented on OAK-9499:
--------------------------------------

After increasing the log severity of [https://github.com/apache/jackrabbit-oak/blob/c6ddcc55bee3de915459af01e91edad32d538f3d/oak-segment-remote/src/main/java/org/apache/jackrabbit/oak/segment/remote/persistentcache/PersistentRedisCache.java#L184] to {{ERROR}} and include the throwable I see

{code}
[pool-3-thread-1] ERROR org.apache.jackrabbit.oak.segment.remote.persistentcache.PersistentRedisCache - Unable to write segment f1632575-99c5-c9f8-f094-20599caf264a to cache: ERR Protocol error: too big inline request
redis.clients.jedis.exceptions.JedisConnectionException: ERR Protocol error: too big inline request
	at redis.clients.jedis.Connection.sendCommand(Connection.java:124)
	at redis.clients.jedis.BinaryClient.set(BinaryClient.java:137)
	at redis.clients.jedis.BinaryJedis.set(BinaryJedis.java:240)
	at org.apache.jackrabbit.oak.segment.remote.persistentcache.PersistentRedisCache.lambda$4(PersistentRedisCache.java:181)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.SocketException: Protocol wrong type for socket (Write failed)
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
	at redis.clients.jedis.util.RedisOutputStream.write(RedisOutputStream.java:73)
	at redis.clients.jedis.util.RedisOutputStream.write(RedisOutputStream.java:66)
	at redis.clients.jedis.Protocol.sendCommand(Protocol.java:101)
	at redis.clients.jedis.Protocol.sendCommand(Protocol.java:85)
	at redis.clients.jedis.Connection.sendCommand(Connection.java:115)
	... 6 more
{code}

> PersistentRedisCacheTest: Test failures
> ---------------------------------------
>
>                 Key: OAK-9499
>                 URL: https://issues.apache.org/jira/browse/OAK-9499
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>            Reporter: Konrad Windszus
>            Priority: Major
>
> I run into the following test failures with the last trunk (https://github.com/apache/jackrabbit-oak/commit/563b834754a1a34f254434f01f7b04626b27374f)
> in module {{oak-segment-remote}}
> {code}
> [ERROR] Tests run: 5, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 9.281 s <<< FAILURE! - in org.apache.jackrabbit.oak.segment.remote.persistentcache.PersistentRedisCacheTest
> [ERROR] testExisting(org.apache.jackrabbit.oak.segment.remote.persistentcache.PersistentRedisCacheTest)  Time elapsed: 1.558 s  <<< FAILURE!
> java.lang.AssertionError: containsSegment failed expected:<0> but was:<750>
> [ERROR] writeAndReadManySegments(org.apache.jackrabbit.oak.segment.remote.persistentcache.PersistentRedisCacheTest)  Time elapsed: 5.962 s  <<< FAILURE!
> java.lang.AssertionError: Wait timeout reached
> [ERROR] testConcurrentWritesSameSegment(org.apache.jackrabbit.oak.segment.remote.persistentcache.PersistentRedisCacheTest)  Time elapsed: 0.333 s  <<< FAILURE!
> java.lang.AssertionError: The segment was not found
> {code}
> This happens reproducibly with 
> {code}
> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
> Maven home: /usr/local/Cellar/maven/3.8.1/libexec
> Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
> Default locale: en_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)