[
https://issues.apache.org/jira/browse/HIVE-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505838#comment-13505838
]
Kevin Wilfong commented on HIVE-3709:
-------------------------------------
I had considered the solution Carl mentioned, but I didn't go that route
because it could result in clutter in the directory specified, in particular we
can't guarantee the file will be deleted in the presence of catastrophic
failures. To solve this the user would need to set up some sort of periodic
cleanup which puts us back in the same position. We might be able to work
around this by regularly touching the file, but I'm not 100% sure.
Carl, are you still seeing threading problems with the most recent patch?
TestHiveServerSessions has been succeeding for me consistently.
> Stop storing default ConfVars in temp file
> ------------------------------------------
>
> Key: HIVE-3709
> URL: https://issues.apache.org/jira/browse/HIVE-3709
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 0.10.0
> Reporter: Kevin Wilfong
> Assignee: Kevin Wilfong
> Attachments: HIVE-3709.1.patch.txt, HIVE-3709.2.patch.txt,
> HIVE-3709.3.patch.txt
>
>
> To work around issues with Hadoop's Configuration object, specifically it's
> addResource(InputStream), default configurations are written to a temp file
> (I think HIVE-2362 introduced this).
> This, however, introduces the problem that once that file is deleted from
> /tmp the client crashes. This is particularly problematic for long running
> services like the metastore server.
> Writing a custom InputStream to deal with the problems in the Configuration
> object should provide a work around, which does not introduce a time bomb
> into Hive.
--
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
