hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <>
Subject [jira] [Created] (HIVE-15893) Followup on HIVE-15671
Date Mon, 13 Feb 2017 19:20:41 GMT
Xuefu Zhang created HIVE-15893:

             Summary: Followup on HIVE-15671
                 Key: HIVE-15893
             Project: Hive
          Issue Type: Improvement
          Components: Spark
    Affects Versions: 2.2.0
            Reporter: Xuefu Zhang
            Assignee: Xuefu Zhang

In HIVE-15671, we fixed a type where server.connect.timeout is used in the place of client.connect.timeout.
This might solve some potential problems, but the original problem reported in HIVE-15671
might still exist. (Not sure if HIVE-15860 helps). Here is the proposal suggested by Marcelo:
bq: server detecting a driver problem after it has connected back to the server.

Hmm. That is definitely not any of the "connect" timeouts, which probably means it isn't configured
and is just using netty's default (which is probably no timeout?). Would probably need something
using io.netty.handler.timeout.IdleStateHandler, and also some periodic "ping" so that the
connection isn't torn down without reason.

We will use this JIRA to track the issue.

This message was sent by Atlassian JIRA

View raw message