AnsweredAssumed Answered

hiveserver1 vs hiveserver2 logging

Question asked by dimamah on Apr 29, 2014
Hello,
It seems that for some reason HS2 outputs far less logging than HS1 in hive 0.12
for example, starting HS1 in the following way : `hive --service hiveserver` 
and executing `show tables` produces this :

`
14/04/30 17:14:16 [pool-1-thread-2] INFO service.HiveServer: Running the query: show tables
14/04/30 17:14:16 [pool-1-thread-2] INFO exec.ListSinkOperator: 1 finished. closing...
14/04/30 17:14:16 [pool-1-thread-2] INFO exec.ListSinkOperator: 1 forwarded 0 rows
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=Driver.run>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=TimeToSubmit>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=compile>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=parse>
14/04/30 17:14:16 [pool-1-thread-2] INFO parse.ParseDriver: Parsing command: show tables
14/04/30 17:14:16 [pool-1-thread-2] INFO parse.ParseDriver: Parse Completed
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=parse start=1398867256379 end=1398867256380 duration=1>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=semanticAnalyze>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: Semantic Analysis Completed
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=semanticAnalyze start=1398867256380 end=1398867256381 duration=1>
14/04/30 17:14:16 [pool-1-thread-2] INFO exec.ListSinkOperator: Initializing Self 2 OP
14/04/30 17:14:16 [pool-1-thread-2] INFO exec.ListSinkOperator: Operator 2 OP initialized
14/04/30 17:14:16 [pool-1-thread-2] INFO exec.ListSinkOperator: Initialization Done 2 OP
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:tab_name, type:string, comment:from deserializer)], properties:null)
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=compile start=1398867256379 end=1398867256384 duration=5>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=Driver.execute>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: Starting command: show tables
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=TimeToSubmit start=1398867256378 end=1398867256384 duration=6>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=runTasks>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=task.DDL.Stage-0>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=task.DDL.Stage-0 start=1398867256384 end=1398867256398 duration=14>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=runTasks start=1398867256384 end=1398867256398 duration=14>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=Driver.execute start=1398867256384 end=1398867256398 duration=14>
OK
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: OK
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: <PERFLOG method=releaseLocks>
14/04/30 17:14:16 [pool-1-thread-2] INFO ql.Driver: </PERFLOG method=releaseLocks start=1398867256398 end=1398867256398 duration=0>
`
  
while when running on HS2 (`hive --service hiveserver2`), the only logging data is from the initialization of the connection:


`
14/04/30 17:18:54 [pool-2-thread-1] INFO cli.CLIService: SessionHandle [4b0a96cb-626b-45ae-ae0d-6a959e84e5a4]: openSession()
14/04/30 17:18:55 [pool-2-thread-1] INFO operation.Operation: Putting temp output to file /tmp/hadoop/4b0a96cb-626b-45ae-ae0d-6a959e84e5a44568051681296760332.pipeout
14/04/30 17:18:55 [pool-2-thread-1] INFO cli.CLIService: SessionHandle [4b0a96cb-626b-45ae-ae0d-6a959e84e5a4]: executeStatement()
14/04/30 17:18:55 [pool-2-thread-1] INFO cli.CLIService: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=01a12804-8f77-4e8f-b17a-de4c39e481c8]: getOperationStatus()
`

And no sign for the executed query. 
The `show tables` is just an example, it also don't show any queries (both mapreduce and direct)


Settings : 
`hive.root.logger` in `hive-log4j.properties` is set to `INFO,console`


Any reason for this?

Thank you, 
Dima.

Outcomes