falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FALCON-885) RequestID is coming as null for all instance API calls
Date Fri, 14 Nov 2014 00:15:34 GMT

    [ https://issues.apache.org/jira/browse/FALCON-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211551#comment-14211551
] 

Venkatesh Seetharam edited comment on FALCON-885 at 11/14/14 12:15 AM:
-----------------------------------------------------------------------

bq. The reason is there is a bad side effect to overloading the thread name. Since thread
name is printed in the logs through %t qualifier, you will notice that thread name has suddenly
become very long 
So what? Its lighter than another threadlocal. The log length remains the same

bq. and request id will be appearing twice in each log, making the log line a bit bulky &
ugly.
Nope, it only appears ONCE


was (Author: svenkat):
bq. The reason is there is a bad side effect to overloading the thread name. Since thread
name is printed in the logs through %t qualifier, you will notice that thread name has suddenly
become very long 
So what? Its lighter than another threadlocal

bq. and request id will be appearing twice in each log, making the log line a bit bulky &
ugly.
Nope, it only appears ONCE

> RequestID is coming as null for all instance API calls
> ------------------------------------------------------
>
>                 Key: FALCON-885
>                 URL: https://issues.apache.org/jira/browse/FALCON-885
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Suhas Vasu
>            Assignee: Venkatesh Seetharam
>             Fix For: 0.6
>
>         Attachments: FALCON-885.patch
>
>
> The Instance API calls are returning null requestID's in all cases. This shouldn't occur.
We need to fix this before we make a release.
> Example API call
> {noformat}
> {"status":"SUCCEEDED","message":"default/SUMMARY\n","requestId":"default/null\n","instancesSummary":[{"cluster":"local","map":{"entry":{"key":"KILLED","value":"3"}}}]}
> {noformat}
> Example CLI command
> {noformat}
> inmobis-MacBook-Pro-3:falcon-0.6-incubating-SNAPSHOT suhas.v$ bin/falcon instance -type
process -kill -name WordCount -start 2014-11-09T19:00Z -end 2014-11-09T22:00Z
> Consolidated Status: SUCCEEDED
> Instances:
> Instance		Cluster		SourceCluster		Status		Start		End		Details					Log
> -----------------------------------------------------------------------------------------------
> 2014-11-09T21:00Z	local	-	KILLED	2014-11-11T06:11Z	2014-11-11T06:14Z	-	http://localhost:11000/oozie?job=0000006-141111114025154-oozie-oozi-W
> 2014-11-09T20:00Z	local	-	KILLED	2014-11-11T06:11Z	2014-11-11T06:14Z	-	http://localhost:11000/oozie?job=0000004-141111114025154-oozie-oozi-W
> 2014-11-09T19:00Z	local	-	KILLED	2014-11-11T06:11Z	2014-11-11T06:14Z	-	http://localhost:11000/oozie?job=0000002-141111114025154-oozie-oozi-W
> Additional Information:
> Response: default/KILL
> Request Id: default/null
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message