You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2021/06/22 17:30:00 UTC

[jira] [Comment Edited] (THRIFT-5434) Eliminate usage of fatal RuntimeException in TSaslServerTransport getTransport

    [ https://issues.apache.org/jira/browse/THRIFT-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367546#comment-17367546 ] 

Jens Geyer edited comment on THRIFT-5434 at 6/22/21, 5:29 PM:
--------------------------------------------------------------

The link seems dubious, ESET warns about it. 
Also, not much information here anyway. Feel free to reopen.


was (Author: jensg):
The link seems dubious, ESET warns about it.

> Eliminate usage of fatal RuntimeException in TSaslServerTransport getTransport
> ------------------------------------------------------------------------------
>
>                 Key: THRIFT-5434
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5434
>             Project: Thrift
>          Issue Type: Improvement
>    Affects Versions: 0.14.2
>            Reporter: Matt McCline
>            Priority: Major
>
> This fatal (Throwable) RuntimeException unnecessarily kills Hive Server 2 and causes user confusion.
> There is a whole blog post explaining it is safe to ignore it, but killing Hive Server 2 is hard to ignore. [“No data or no sasl data in the stream” Error in HiveServer2 Log – Hadoop Troubleshooting Guide – Eric's Blog (ericlin.me)|https://cloudera.ericlin.me/2017/09/no-data-or-no-sasl-data-in-the-stream-error-in-hiveserver2-log/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)