[
https://issues.apache.org/jira/browse/HBASE-19210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16251772#comment-16251772
]
Ted Yu commented on HBASE-19210:
--------------------------------
bq. Can you try figuring out if it is a client or server caused error?
I think after upgrading jackson (HBASE-16338), interaction between client and
REST changed, resulting in NoHttpResponseException / SocketException on the
client side. The exception is for invalid request so tweaking test should be
enough.
bq. Does getting a new client make the error go away?
As shown in addendum 2, client can still talk to REST server after getting the
exception.
bq. Is it a problem with too many server errors
I don't think so - there are only two invalid requests before getting the
exception.
> TestNamespacesInstanceResource fails
> ------------------------------------
>
> Key: HBASE-19210
> URL: https://issues.apache.org/jira/browse/HBASE-19210
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0-beta-1
>
> Attachments: 19210.addendum, 19210.v1.txt, 19210.v1.txt,
> 19210.v2.txt, 19210.v3.txt, HBASE-19210.WIP.patch
>
>
> This is the top flaky test.
> The following can be reproduced:
> {code}
> java.net.SocketException: Connection reset
> at
> org.apache.hadoop.hbase.rest.TestNamespacesInstanceResource.testInvalidNamespacePostsAndPuts(TestNamespacesInstanceResource.java:271)
> {code}
> With commit e320df5a0c267258c03909da8d0eee4c0e287532, the test passes.
> With commit 5facaded902a13556952b1f9d26b768cb86e6599, the test fails.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
