[
https://issues.apache.org/jira/browse/HDFS-11948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16087993#comment-16087993
]
Anu Engineer commented on HDFS-11948:
-------------------------------------
[~szetszwo] Thanks for uploading the patch. From code changes perspective this
looks good. I think the unit test failure is related to this patch.
{code}
2017-07-14 13:21:13,357 [Thread-624] INFO impl.LeaderElection
(LeaderElection.java:askForVotes(127)) - 127.0.0.1:53437: begin an election in
Term 592
2017-07-14 13:21:13,367 [nioEventLoopGroup-7-4] WARN
channel.DefaultChannelPipeline (Slf4JLogger.java:warn(151)) - An
exceptionCaught() event was fired, and it reached at the tail of the pipeline.
It usually means the last handler in the pipeline did not handle the exception.
java.lang.IllegalStateException: STATE MISMATCHED: In 127.0.0.1:53431, current
state STARTING is not one of the expected states [RUNNING]
{code}
I think on the server side we are not catching some exception and it is caught
by netty default handler on the server side, hence that error is not propagated
to the client side.
Also in the profiler, I see around 2025 threads being launched for this single
test. Thought you might be interested in that.
> Ozone: change TestRatisManager to check cluster with data
> ---------------------------------------------------------
>
> Key: HDFS-11948
> URL: https://issues.apache.org/jira/browse/HDFS-11948
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Attachments: HDFS-11948-HDFS-7240.20170614.patch
>
>
> TestRatisManager first creates multiple Ratis clusters. Then it changes the
> membership and closes some clusters. However, it does not test the clusters
> with data.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
