[
https://issues.apache.org/jira/browse/HIVE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sichi updated HIVE-2181:
-----------------------------
Status: Open (was: Patch Available)
I ran TestHiveServer, and even though it passed, I saw the exception below in
the test output. That's because one of the test cases leaves the socket in
use, so the second one fails to open it.
Rather than actually starting the server, maybe just unit-test the cleanup
method in isolation?
{noformat}
[junit] org.apache.thrift.transport.TTransportException: Could not create
ServerSocket on address 0.0.0.0/0.0.0.0:10000.
[junit] at
org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:93)
[junit] at
org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:75)
[junit] at
org.apache.thrift.transport.TServerSocket.<init>(TServerSocket.java:68)
[junit] at
org.apache.hadoop.hive.service.HiveServer.main(HiveServer.java:688)
[junit] at
org.apache.hadoop.hive.service.TestHiveServer$2.run(TestHiveServer.java:423)
[junit] ------------- ---------------- ---------------
[junit]
{noformat}
> Clean up the scratch.dir (tmp/hive-root) while restarting Hive server.
> ------------------------------------------------------------------------
>
> Key: HIVE-2181
> URL: https://issues.apache.org/jira/browse/HIVE-2181
> Project: Hive
> Issue Type: Bug
> Components: Server Infrastructure
> Affects Versions: 0.8.0
> Environment: Suse linux, Hadoop 20.1, Hive 0.8
> Reporter: sanoj mathew
> Assignee: Chinna Rao Lalam
> Priority: Minor
> Attachments: HIVE-2181.1.patch, HIVE-2181.2.patch, HIVE-2181.3.patch,
> HIVE-2181.4.patch, HIVE-2181.5.patch, HIVE-2181.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Now queries leaves the map outputs under scratch.dir after execution. If the
> hive server is stopped we need not keep the stopped server's map oputputs. So
> whle starting the server we can clear the scratch.dir. This can help in
> improved disk usage.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
