[
https://issues.apache.org/jira/browse/HIVE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505273#comment-13505273
]
Carl Steinbach commented on HIVE-3596:
--------------------------------------
@Chris: Turns out that Kevin has been working on this same problem in
HIVE-3709. He was able to get a little bit farther, but his solution seems to
have some concurrency issues. If you have time it may be worth looking at his
solution and seeing if you can spot threading problem.
> Regression - HiveConf static variable causes issues in long running JVM
> instances with /tmp/ data
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-3596
> URL: https://issues.apache.org/jira/browse/HIVE-3596
> Project: Hive
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 0.8.0, 0.8.1, 0.9.0
> Reporter: Chris McConnell
> Assignee: Chris McConnell
> Fix For: 0.8.1, 0.9.0, 0.10.0
>
> Attachments: HIVE-3596.patch
>
>
> With Hive 0.8.x, HiveConf was changed to utilize the private, static member
> "confVarURL" which points to /tmp/hive-<user>-<tmp_number>.xml for job
> configuration settings.
> During long running JVMs, such as a Beeswax server, which creates multiple
> HiveConf objects over time this variable does not properly get updated
> between jobs and can cause job failure if the OS cleans /tmp/ during a cron
> job.
--
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
