[jira] [Created] (HIVE-24284) NPE when parsing druid logs using Hive

2020-10-18 Thread mahesh kumar behera (Jira) 
mahesh kumar behera created HIVE-24284:
--

 Summary: NPE when parsing druid logs using Hive
 Key: HIVE-24284
 URL: https://issues.apache.org/jira/browse/HIVE-24284
 Project: Hive
  Issue Type: Bug
  Components: Hive
Reporter: mahesh kumar behera
Assignee: mahesh kumar behera


As per current Sys-logger parser, its always expecting a valid proc id. But as 
per RFC3164 and RFC5424, the proc id can be skipped.So hive should handled it 
by using NILVALUE/empty string in case the proc id is null.

 
{code:java}
Caused by: java.lang.NullPointerException: null
at java.lang.String.(String.java:566)
at 
org.apache.hadoop.hive.ql.log.syslog.SyslogParser.createEvent(SyslogParser.java:361)
at 
org.apache.hadoop.hive.ql.log.syslog.SyslogParser.readEvent(SyslogParser.java:326)
at 
org.apache.hadoop.hive.ql.log.syslog.SyslogSerDe.deserialize(SyslogSerDe.java:95)
 {code}



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

[jira] [Created] (HIVE-24283) Memory leak problem of hiveserver2 when compiling in parallel

2020-10-18 Thread zhaolun7 (Jira) 
zhaolun7 created HIVE-24283:
---

 Summary: Memory leak problem of hiveserver2 when compiling in 
parallel
 Key: HIVE-24283
 URL: https://issues.apache.org/jira/browse/HIVE-24283
 Project: Hive
  Issue Type: Bug
  Components: HiveServer2, JDBC
Affects Versions: 2.3.7
 Environment: CentOS 7.2

openjdk 8

Hadoop 2.9.2

Hive 2.3.7
Reporter: zhaolun7
 Fix For: 2.3.7
 Attachments: image-2020-10-18-22-25-44-271.png, 
image-2020-10-18-22-26-20-436.png

I used JDBC to connect to HIVESERVER2 and got about 25,000 SQL statements as 
test data from the production environment to test parallel compilation. Then 
save the memory snapshot of hiveserver2. Then run the test again and save the 
memory snapshot. I found that the memory occupied became larger and the second 
time running was more slower.

 

This is the first time I have submitted an issue. If there is any incomplete 
description, please point it out. If the format of the issue is incorrect, 
please help me modify it, thank you

 

!image-2020-10-18-22-26-20-436.png!

!image-2020-10-18-22-25-44-271.png!

 
 



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