[
https://issues.apache.org/jira/browse/HIVE-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662448#comment-14662448
]
Jason Dere commented on HIVE-11466:
-----------------------------------
Looks like there was a bad merge of ThriftBinaryCLIService.java, and
server.serve() is called twice. I commented out the first invocation and it
looks like the log size isn't huge anymore.
{noformat}
// TCP Server
server = new TThreadPoolServer(sargs);
+ server.setServerEventHandler(serverEventHandler);
+ server.serve();
- String msg = "Started " + ThriftBinaryCLIService.class.getSimpleName()
+ " on port "
+ String msg = "Starting " + ThriftBinaryCLIService.class.getSimpleName()
+ " on port "
+ portNum + " with " + minWorkerThreads + "..." + maxWorkerThreads
+ " worker threads";
LOG.info(msg);
+ server.serve();
} catch (Throwable t) {
{noformat}
> HIVE-10166 generates more data on hive.log causing Jenkins to fill all the
> disk.
> --------------------------------------------------------------------------------
>
> Key: HIVE-11466
> URL: https://issues.apache.org/jira/browse/HIVE-11466
> Project: Hive
> Issue Type: Bug
> Reporter: Sergio Peña
> Assignee: Xuefu Zhang
> Attachments: HIVE-11466.patch
>
>
> An issue with HIVE-10166 patch is increasing the size of hive.log and
> causing jenkins to fail because it does not have more space.
> Here's a test I run when running TestJdbcWithMiniHS2 before the patch, with
> the patch, and after other commits.
> {noformat}
> BEFORE HIVE-10166
> 13M Aug 5 11:57 ./hive-unit/target/tmp/log/hive.log
> WITH HIVE-10166
> 2.4G Aug 5 12:07 ./hive-unit/target/tmp/log/hive.log
> CURRENT HEAD
> 3.2G Aug 5 12:36 ./hive-unit/target/tmp/log/hive.log
> {noformat}
> This is just a single test, but on Jenkins, hive.log is more than 13G of size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
