[jira] [Updated] (RATIS-200) TestRaftStream#testWriteWithOffset sometimes fails with assertion
[ https://issues.apache.org/jira/browse/RATIS-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated RATIS-200: - Attachment: testRaftStream-output.txt > TestRaftStream#testWriteWithOffset sometimes fails with assertion > - > > Key: RATIS-200 > URL: https://issues.apache.org/jira/browse/RATIS-200 > Project: Ratis > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Attachments: testRaftStream-output.txt > > > {code} > testWriteWithOffset(org.apache.ratis.grpc.TestRaftStream) Time elapsed: > 1.253 sec <<< FAILURE! > java.lang.AssertionError: expected:<8> but was:<9> > at > org.apache.ratis.grpc.TestRaftStream.testWriteWithOffset(TestRaftStream.java:240) > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RATIS-200) TestRaftStream#testWriteWithOffset sometimes fails with assertion
Ted Yu created RATIS-200: Summary: TestRaftStream#testWriteWithOffset sometimes fails with assertion Key: RATIS-200 URL: https://issues.apache.org/jira/browse/RATIS-200 Project: Ratis Issue Type: Test Reporter: Ted Yu {code} testWriteWithOffset(org.apache.ratis.grpc.TestRaftStream) Time elapsed: 1.253 sec <<< FAILURE! java.lang.AssertionError: expected:<8> but was:<9> at org.apache.ratis.grpc.TestRaftStream.testWriteWithOffset(TestRaftStream.java:240) {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RATIS-195) TestRaftReconfigurationWithSimulatedRpc fails with assertion error
[ https://issues.apache.org/jira/browse/RATIS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336368#comment-16336368 ] Ted Yu commented on RATIS-195: -- Got the following failure for variant of TestRaftReconfiguration : TestRaftReconfigurationWithGRpc>RaftReconfigurationBaseTest.testRevertConfigurationChange:572 expected: but was: > TestRaftReconfigurationWithSimulatedRpc fails with assertion error > -- > > Key: RATIS-195 > URL: https://issues.apache.org/jira/browse/RATIS-195 > Project: Ratis > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Attachments: > org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc-output.txt, > ratis-8464.tst, testRaftReconfigurationWithSimulatedRpc-linux-output.txt > > > As of commit 7b3a9a6f5f8e8075727d84e3ddeae7b594eda89c, I observed the > following : > {code} > testRevertConfigurationChange(org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc) > Time elapsed: 2.119 sec <<< FAILURE! > java.lang.AssertionError: 1 0 expected: but was: > {code} > 1 was confIndex and 0 was log.getLastCommittedIndex() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RATIS-199) TestStateMachine times out
[ https://issues.apache.org/jira/browse/RATIS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336284#comment-16336284 ] Ted Yu commented on RATIS-199: -- This could be dupe of RATIS-195 where bunch of tests using SimulatedRpc fail. MiniRaftClusterWithSimulatedRpc is used for TestStateMachine. > TestStateMachine times out > -- > > Key: RATIS-199 > URL: https://issues.apache.org/jira/browse/RATIS-199 > Project: Ratis > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Attachments: testStateMachine-output.txt > > > TestStateMachine times out when run as part of the test suite. > This was as of commit 0f7169db51ba15108c265b1e937e9daeaa085045 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RATIS-184) Document how to deploy the snapshot artifacts
[ https://issues.apache.org/jira/browse/RATIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336175#comment-16336175 ] Tsz Wo Nicholas Sze commented on RATIS-184: --- r184_20180123.patch: addresses Mukul's review comments. > Document how to deploy the snapshot artifacts > - > > Key: RATIS-184 > URL: https://issues.apache.org/jira/browse/RATIS-184 > Project: Ratis > Issue Type: Task >Reporter: Tsz Wo Nicholas Sze >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Attachments: r184_20180105.patch, r184_20180123.patch > > > We should add instructions for deploy a snapshot to "How to deploy" in > BUILDING.md. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-184) Document how to deploy the snapshot artifacts
[ https://issues.apache.org/jira/browse/RATIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-184: -- Attachment: r184_20180123.patch > Document how to deploy the snapshot artifacts > - > > Key: RATIS-184 > URL: https://issues.apache.org/jira/browse/RATIS-184 > Project: Ratis > Issue Type: Task >Reporter: Tsz Wo Nicholas Sze >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Attachments: r184_20180105.patch, r184_20180123.patch > > > We should add instructions for deploy a snapshot to "How to deploy" in > BUILDING.md. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RATIS-199) TestStateMachine times out
Ted Yu created RATIS-199: Summary: TestStateMachine times out Key: RATIS-199 URL: https://issues.apache.org/jira/browse/RATIS-199 Project: Ratis Issue Type: Test Reporter: Ted Yu Attachments: testStateMachine-output.txt TestStateMachine times out when run as part of the test suite. This was as of commit 0f7169db51ba15108c265b1e937e9daeaa085045 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RATIS-199) TestStateMachine times out
[ https://issues.apache.org/jira/browse/RATIS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336126#comment-16336126 ] Ted Yu commented on RATIS-199: -- Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T07:58:13Z) Maven home: /mnt/disk2/a/apache-maven-3.5.2 Java version: 1.8.0_161, vendor: Oracle Corporation Java home: /mnt/disk2/a/jdk1.8.0_161/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-327.28.3.el7.x86_64", arch: "amd64", family: "unix" > TestStateMachine times out > -- > > Key: RATIS-199 > URL: https://issues.apache.org/jira/browse/RATIS-199 > Project: Ratis > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Attachments: testStateMachine-output.txt > > > TestStateMachine times out when run as part of the test suite. > This was as of commit 0f7169db51ba15108c265b1e937e9daeaa085045 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-199) TestStateMachine times out
[ https://issues.apache.org/jira/browse/RATIS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated RATIS-199: - Attachment: testStateMachine-output.txt > TestStateMachine times out > -- > > Key: RATIS-199 > URL: https://issues.apache.org/jira/browse/RATIS-199 > Project: Ratis > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Attachments: testStateMachine-output.txt > > > TestStateMachine times out when run as part of the test suite. > This was as of commit 0f7169db51ba15108c265b1e937e9daeaa085045 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RATIS-184) Document how to deploy the snapshot artifacts
[ https://issues.apache.org/jira/browse/RATIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336112#comment-16336112 ] Tsz Wo Nicholas Sze commented on RATIS-184: --- Thanks [~msingh] for reviewing and trying it out. For gpg, it seems too much to describe it Ratis doc. Let me also add a link for it. > Document how to deploy the snapshot artifacts > - > > Key: RATIS-184 > URL: https://issues.apache.org/jira/browse/RATIS-184 > Project: Ratis > Issue Type: Task >Reporter: Tsz Wo Nicholas Sze >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Attachments: r184_20180105.patch > > > We should add instructions for deploy a snapshot to "How to deploy" in > BUILDING.md. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RATIS-195) TestRaftReconfigurationWithSimulatedRpc fails with assertion error
[ https://issues.apache.org/jira/browse/RATIS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16336080#comment-16336080 ] Ted Yu commented on RATIS-195: -- Here are the failed tests related to SimulatedRpc : {code} Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 56.851 sec <<< FAILURE! - in org.apache.ratis.server.simulation.TestLeaderElectionWithSimulatedRpc -- Running org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc Tests run: 12, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 200.222 sec <<< FAILURE! - in org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc -- testReconfTwice(org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc) Time elapsed: 11.981 sec <<< FAILURE! -- Running org.apache.ratis.server.simulation.TestReinitializationWithSimulatedRpc Tests run: 4, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 177.503 sec <<< FAILURE! - in org.apache.ratis.server.simulation.TestReinitializationWithSimulatedRpc {code} > TestRaftReconfigurationWithSimulatedRpc fails with assertion error > -- > > Key: RATIS-195 > URL: https://issues.apache.org/jira/browse/RATIS-195 > Project: Ratis > Issue Type: Test >Reporter: Ted Yu >Priority: Minor > Attachments: > org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc-output.txt, > ratis-8464.tst, testRaftReconfigurationWithSimulatedRpc-linux-output.txt > > > As of commit 7b3a9a6f5f8e8075727d84e3ddeae7b594eda89c, I observed the > following : > {code} > testRevertConfigurationChange(org.apache.ratis.server.simulation.TestRaftReconfigurationWithSimulatedRpc) > Time elapsed: 2.119 sec <<< FAILURE! > java.lang.AssertionError: 1 0 expected: but was: > {code} > 1 was confIndex and 0 was log.getLastCommittedIndex() -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-198) Ozone Ratis test is failing with Socket IO exception during Key Creation
[ https://issues.apache.org/jira/browse/RATIS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-198: -- Attachment: HDFS-12794-HDFS-7240.009.patch_tmp > Ozone Ratis test is failing with Socket IO exception during Key Creation > > > Key: RATIS-198 > URL: https://issues.apache.org/jira/browse/RATIS-198 > Project: Ratis > Issue Type: Bug >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Attachments: HDFS-12794-HDFS-7240.009.patch_tmp > > > While Executing TestCorona#ratisTest3, with the attached patch hit the below > exception. > {code:java} > 2018-01-23 18:15:11,058 [IPC Server handler 5 on 51292] INFO > scm.StorageContainerManager > (StorageContainerManager.java:notifyObjectStageChange(687)) - Object type > container name 2efd4054-c479-45a4-a1db-3a4ec3526d4d op create new stage > complete > 100.00% > |█| > 20/20 Time: 0:00:05 > Jan 23, 2018 6:15:11 PM > org.apache.ratis.shaded.io.grpc.internal.ManagedChannelImpl > maybeTerminateChannel > INFO: [ManagedChannelImpl@7202ef94] Terminated > Jan 23, 2018 6:15:11 PM > org.apache.ratis.shaded.io.grpc.internal.ManagedChannelImpl > maybeTerminateChannel > INFO: [ManagedChannelImpl@5e5452c3] Terminated > Jan 23, 2018 6:15:11 PM > org.apache.ratis.shaded.io.grpc.internal.ManagedChannelImpl > maybeTerminateChannel > INFO: [ManagedChannelImpl@72d74e90] Terminated > Jan 23, 2018 6:15:11 PM > org.apache.ratis.shaded.io.grpc.internal.ManagedChannelImpl > maybeTerminateChannel > INFO: [ManagedChannelImpl@3679cc6c] Terminated > Jan 23, 2018 6:15:11 PM > org.apache.ratis.shaded.io.grpc.internal.ManagedChannelImpl > maybeTerminateChannel > INFO: [ManagedChannelImpl@589f60fd] Terminated > Jan 23, 2018 6:15:11 PM > org.apache.ratis.shaded.io.grpc.netty.NettyServerHandler onConnectionError > WARNING: Connection Error > java.io.IOException: Connection reset by peer > at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > at sun.nio.ch.IOUtil.read(IOUtil.java:192) > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) > at > org.apache.ratis.shaded.io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288) > {code}{code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RATIS-197) Reads are failing in Ozone for keys of size greater than 4MB
Mukul Kumar Singh created RATIS-197: --- Summary: Reads are failing in Ozone for keys of size greater than 4MB Key: RATIS-197 URL: https://issues.apache.org/jira/browse/RATIS-197 Project: Ratis Issue Type: Bug Affects Versions: 0.2.0-alpha Reporter: Mukul Kumar Singh Assignee: Mukul Kumar Singh Fix For: 0.2.0-alpha Read of keys are failing in Ozone with the following exception. {code} an 23, 2018 6:25:44 AM org.apache.ratis.shaded.io.grpc.netty.NettyServerHandler onStreamError WARNING: Stream Error org.apache.ratis.shaded.io.netty.handler.codec.http2.Http2Exception$StreamException: Stream closed before write could take place at org.apache.ratis.shaded.io.netty.handler.codec.http2.Http2Exception.streamError(Http2Exception.java:149) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController$FlowState.cancel(DefaultHttp2RemoteFlowController.java:487) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController$FlowState.cancel(DefaultHttp2RemoteFlowController.java:468) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController$1.onStreamClosed(DefaultHttp2RemoteFlowController.java:103) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2Connection.notifyClosed(DefaultHttp2Connection.java:343) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2Connection$ActiveStreams.removeFromActiveStreams(DefaultHttp2Connection.java:1151) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2Connection$ActiveStreams.deactivate(DefaultHttp2Connection.java:1099) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2Connection$DefaultStream.close(DefaultHttp2Connection.java:521) at org.apache.ratis.shaded.io.netty.handler.codec.http2.DefaultHttp2Connection.close(DefaultHttp2Connection.java:149) at org.apache.ratis.shaded.io.netty.handler.codec.http2.Http2ConnectionHandler$BaseDecoder.channelInactive(Http2ConnectionHandler.java:181) at org.apache.ratis.shaded.io.netty.handler.codec.http2.Http2ConnectionHandler.channelInactive(Http2ConnectionHandler.java:372) at org.apache.ratis.shaded.io.grpc.netty.NettyServerHandler.channelInactive(NettyServerHandler.java:280) at org.apache.ratis.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:255) at org.apache.ratis.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:241) at org.apache.ratis.shaded.io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:234) at org.apache.ratis.shaded.io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1329) at org.apache.ratis.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:255) at org.apache.ratis.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:241) at org.apache.ratis.shaded.io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:908) at org.apache.ratis.shaded.io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:744) at org.apache.ratis.shaded.io.netty.util.concurrent.SingleThreadEventExecutor.safeExecute(SingleThreadEventExecutor.java:451) at org.apache.ratis.shaded.io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418) at org.apache.ratis.shaded.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:401) at org.apache.ratis.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:877) at org.apache.ratis.shaded.io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) at java.lang.Thread.run(Thread.java:745) {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)