[jira] [Updated] (HIVE-4766) Support HS2 client login timeout when the thrift thread max# is reached

2014-11-25 Thread Chaoyu Tang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaoyu Tang updated HIVE-4766:
--
Attachment: HIVE-4766.2.patch

Thanks, [~leftylev]. Updated the patch based on your comments

 Support HS2 client login timeout when the thrift thread max# is reached
 ---

 Key: HIVE-4766
 URL: https://issues.apache.org/jira/browse/HIVE-4766
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.10.0
Reporter: Chaoyu Tang
Assignee: Chaoyu Tang
  Labels: TODOC15
 Fix For: 0.15.0, 0.14.1

 Attachments: HIVE-4766.1.patch, HIVE-4766.2.patch, HIVE-4766.patch


 HiveServer2 client (beeline) hangs in login if the thrift max thread# has 
 been reached. It is because the server crashes due to a defect in currently 
 used thrift 0.9.0. When hive is upgraded to use a new version of Thrift (say 
 thrift 1.0), HS2 should support client login timeout instead of current 
 hanging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-4766) Support HS2 client login timeout when the thrift thread max# is reached

2014-11-25 Thread Szehon Ho (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Szehon Ho updated HIVE-4766:

   Resolution: Fixed
Fix Version/s: (was: 0.14.1)
   Status: Resolved  (was: Patch Available)

Committed to trunk.  Thanks Chaoyu!

 Support HS2 client login timeout when the thrift thread max# is reached
 ---

 Key: HIVE-4766
 URL: https://issues.apache.org/jira/browse/HIVE-4766
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.10.0
Reporter: Chaoyu Tang
Assignee: Chaoyu Tang
  Labels: TODOC15
 Fix For: 0.15.0

 Attachments: HIVE-4766.1.patch, HIVE-4766.2.patch, HIVE-4766.patch


 HiveServer2 client (beeline) hangs in login if the thrift max thread# has 
 been reached. It is because the server crashes due to a defect in currently 
 used thrift 0.9.0. When hive is upgraded to use a new version of Thrift (say 
 thrift 1.0), HS2 should support client login timeout instead of current 
 hanging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-4766) Support HS2 client login timeout when the thrift thread max# is reached

2014-11-24 Thread Chaoyu Tang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaoyu Tang updated HIVE-4766:
--
Attachment: HIVE-4766.1.patch

Thanks, [~szehon]. I have addressed all the issues you raised in  the patch 
review. The two new configurations added are:
1. hive.server2.thrift.login.timeout -- Timeout for thrift clients during login 
to HiveServer2
2. hive.server2.thrift.exponential.backoff.slot.length -- Binary exponential 
backoff slot time for thrift clients during login to HiveServer2, for retries 
until hitting thrift client timeout
I have also manually tested the time unit conversion as you suggested.
I uploaded this patch to RB: https://reviews.apache.org/r/28416/ , note that 
the empty spaces (red blocks) shown in RB code have been removed in this 
attached patch.

 Support HS2 client login timeout when the thrift thread max# is reached
 ---

 Key: HIVE-4766
 URL: https://issues.apache.org/jira/browse/HIVE-4766
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.10.0
Reporter: Chaoyu Tang
Assignee: Chaoyu Tang
  Labels: TODOC15
 Fix For: 0.15.0, 0.14.1

 Attachments: HIVE-4766.1.patch, HIVE-4766.patch


 HiveServer2 client (beeline) hangs in login if the thrift max thread# has 
 been reached. It is because the server crashes due to a defect in currently 
 used thrift 0.9.0. When hive is upgraded to use a new version of Thrift (say 
 thrift 1.0), HS2 should support client login timeout instead of current 
 hanging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-4766) Support HS2 client login timeout when the thrift thread max# is reached

2014-11-22 Thread Chaoyu Tang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaoyu Tang updated HIVE-4766:
--
Fix Version/s: 0.14.1
   0.15.0
   Labels: TODOC15  (was: )
   Status: Patch Available  (was: Open)

 Support HS2 client login timeout when the thrift thread max# is reached
 ---

 Key: HIVE-4766
 URL: https://issues.apache.org/jira/browse/HIVE-4766
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.10.0
Reporter: Chaoyu Tang
Assignee: Chaoyu Tang
  Labels: TODOC15
 Fix For: 0.15.0, 0.14.1

 Attachments: HIVE-4766.patch


 HiveServer2 client (beeline) hangs in login if the thrift max thread# has 
 been reached. It is because the server crashes due to a defect in currently 
 used thrift 0.9.0. When hive is upgraded to use a new version of Thrift (say 
 thrift 1.0), HS2 should support client login timeout instead of current 
 hanging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-4766) Support HS2 client login timeout when the thrift thread max# is reached

2014-11-22 Thread Chaoyu Tang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaoyu Tang updated HIVE-4766:
--
Attachment: HIVE-4766.patch

Hive has upgraded to use Thrift-0.92 (See HIVE-8829) which includes THRIFT-2046 
that provides the supports to loginTimeout and binary exponential backoff 
algorithm in login retry interval. Change Hive to adopt these features.
Two new configurations are introduced:
1. hive.server2.thrift.login.timeout -- timeout for the thrift client to login 
(in seconds)
2. hive.server2.thrift.exponential.backoff.slotlength: Slot time of binary 
exponential backoff algorithm that HS2 Thrift Server uses for its login retry


 Support HS2 client login timeout when the thrift thread max# is reached
 ---

 Key: HIVE-4766
 URL: https://issues.apache.org/jira/browse/HIVE-4766
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.10.0
Reporter: Chaoyu Tang
Assignee: Chaoyu Tang
  Labels: TODOC15
 Fix For: 0.15.0, 0.14.1

 Attachments: HIVE-4766.patch


 HiveServer2 client (beeline) hangs in login if the thrift max thread# has 
 been reached. It is because the server crashes due to a defect in currently 
 used thrift 0.9.0. When hive is upgraded to use a new version of Thrift (say 
 thrift 1.0), HS2 should support client login timeout instead of current 
 hanging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-4766) Support HS2 client login timeout when the thrift thread max# is reached

2013-06-20 Thread Chaoyu Tang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chaoyu Tang updated HIVE-4766:
--

  Component/s: HiveServer2
  Description: HiveServer2 client (beeline) hangs in login if the 
thrift max thread# has been reached. It is because the server crashes due to a 
defect in currently used thrift 0.9.0. When hive is upgraded to use a new 
version of Thrift (say thrift 1.0), HS2 should support client login timeout 
instead of current hanging.
Affects Version/s: 0.10.0
   Issue Type: Improvement  (was: Bug)
  Summary: Support HS2 client login timeout when the thrift thread 
max# is reached  (was: HS2 login timeout )

 Support HS2 client login timeout when the thrift thread max# is reached
 ---

 Key: HIVE-4766
 URL: https://issues.apache.org/jira/browse/HIVE-4766
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.10.0
Reporter: Chaoyu Tang

 HiveServer2 client (beeline) hangs in login if the thrift max thread# has 
 been reached. It is because the server crashes due to a defect in currently 
 used thrift 0.9.0. When hive is upgraded to use a new version of Thrift (say 
 thrift 1.0), HS2 should support client login timeout instead of current 
 hanging.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira