[jira] [Updated] (YARN-3560) Not able to navigate to the cluster from tracking url (proxy) generated after submission of job

2015-05-18 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3560:
--
Assignee: (was: Anushri)

> Not able to navigate to the cluster from tracking url (proxy) generated after 
> submission of job
> ---
>
> Key: YARN-3560
> URL: https://issues.apache.org/jira/browse/YARN-3560
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Anushri
>Priority: Minor
> Attachments: YARN-3560.patch
>
>
> a standalone web proxy server is enabled in the cluster
> when a job is submitted the url generated contains proxy
> track this url
> in the web page , if we try to navigate to the cluster links [about. 
> applications, or scheduler] it gets redirected to some default port instead 
> of actual RM web port configured
> as such it throws "webpage not available"



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


[jira] [Updated] (YARN-3560) Not able to navigate to the cluster from tracking url (proxy) generated after submission of job

2015-05-18 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3560:
--
Assignee: Anushri

> Not able to navigate to the cluster from tracking url (proxy) generated after 
> submission of job
> ---
>
> Key: YARN-3560
> URL: https://issues.apache.org/jira/browse/YARN-3560
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Anushri
>Assignee: Anushri
>Priority: Minor
> Attachments: YARN-3560.patch
>
>
> a standalone web proxy server is enabled in the cluster
> when a job is submitted the url generated contains proxy
> track this url
> in the web page , if we try to navigate to the cluster links [about. 
> applications, or scheduler] it gets redirected to some default port instead 
> of actual RM web port configured
> as such it throws "webpage not available"



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


[jira] [Commented] (YARN-3631) Tracking URI for killed applications

2015-05-12 Thread Anushri (JIRA)

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

Anushri commented on YARN-3631:
---

When the link is clicked , it is directed to simply the applications list of 
cluster. So the link can be renamed something in accordance. As the link is 
named "History" but , it's not redirected to JHS.

> Tracking URI for killed applications
> 
>
> Key: YARN-3631
> URL: https://issues.apache.org/jira/browse/YARN-3631
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Anushri
>Priority: Minor
>
> If some running application is killed we can't track it in JHS
> but still at UI the tracking URI even for killed application is given as 
> "History" 
> Also the REST API returns the link to trace it in "cluster- applications" 
> list.



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


[jira] [Updated] (YARN-3631) Tracking URI for killed applications

2015-05-12 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3631:
--
Description: 
If some running application is killed we can't track it in JHS
but still at UI the tracking URI even for killed application is given as 
"History" 

Also the REST API returns the link to trace it in "cluster- applications" list.

  was:If some running application is killed, we can't trace it in JHS .


> Tracking URI for killed applications
> 
>
> Key: YARN-3631
> URL: https://issues.apache.org/jira/browse/YARN-3631
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Anushri
>Priority: Minor
>
> If some running application is killed we can't track it in JHS
> but still at UI the tracking URI even for killed application is given as 
> "History" 
> Also the REST API returns the link to trace it in "cluster- applications" 
> list.



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


[jira] [Created] (YARN-3631) Tracking URI for killed applications

2015-05-12 Thread Anushri (JIRA)
Anushri created YARN-3631:
-

 Summary: Tracking URI for killed applications
 Key: YARN-3631
 URL: https://issues.apache.org/jira/browse/YARN-3631
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Anushri
Priority: Minor


If some running application is killed, we can't trace it in JHS .



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


[jira] [Commented] (YARN-3576) In Log - Container getting killed by AM even when work preserving is enabled

2015-05-06 Thread Anushri (JIRA)

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

Anushri commented on YARN-3576:
---

job running - pi
no of mappers - 10

in AM logs it's mentioned - Container killed on request

> In Log - Container getting killed by AM even when work preserving is enabled 
> -
>
> Key: YARN-3576
> URL: https://issues.apache.org/jira/browse/YARN-3576
> Project: Hadoop YARN
>  Issue Type: Bug
> Environment: SUSE11 SP3
> 3 nodes cluster
>Reporter: Anushri
>Priority: Minor
>
> RM in HA mode
> NM running on one node
> work preserving enabled
> RM in HA mode one NM running work preserving is enabled An application is 
> submitted and RM switch over happens. In the NM log it is found that AM kills 
> some of the containers and those containers have exit code as 143. but in the 
> container logs , logs are found for the same container. 
> Problem : 
> if work preserving is enabled why is it killing and cleaning the container? 
> and if the container is getting killed , why is its log present in container 
> logs?



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


[jira] [Created] (YARN-3576) In Log - Container getting killed by AM even when work preserving is enabled

2015-05-05 Thread Anushri (JIRA)
Anushri created YARN-3576:
-

 Summary: In Log - Container getting killed by AM even when work 
preserving is enabled 
 Key: YARN-3576
 URL: https://issues.apache.org/jira/browse/YARN-3576
 Project: Hadoop YARN
  Issue Type: Bug
 Environment: SUSE11 SP3
3 nodes cluster
Reporter: Anushri
Priority: Minor


RM in HA mode
NM running on one node
work preserving enabled

RM in HA mode one NM running work preserving is enabled An application is 
submitted and RM switch over happens. In the NM log it is found that AM kills 
some of the containers and those containers have exit code as 143. but in the 
container logs , logs are found for the same container. 
Problem : 
if work preserving is enabled why is it killing and cleaning the container? 
and if the container is getting killed , why is its log present in container 
logs?



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


[jira] [Created] (YARN-3560) Not able to navigate to the cluster from tracking url (proxy) generated after submission of job

2015-04-29 Thread Anushri (JIRA)
Anushri created YARN-3560:
-

 Summary: Not able to navigate to the cluster from tracking url 
(proxy) generated after submission of job
 Key: YARN-3560
 URL: https://issues.apache.org/jira/browse/YARN-3560
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Anushri
Priority: Minor


a standalone web proxy server is enabled in the cluster
when a job is submitted the url generated contains proxy
track this url
in the web page , if we try to navigate to the cluster links [about. 
applications, or scheduler] it gets redirected to some default port instead of 
actual RM web port configured
as such it throws "webpage not available"



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


[jira] [Updated] (YARN-3189) Yarn application usage command should not give -appstate and -apptype

2015-03-27 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3189:
--
Attachment: YARN-3189_1.patch

modified the test cases

> Yarn application usage command should not give -appstate and -apptype
> -
>
> Key: YARN-3189
> URL: https://issues.apache.org/jira/browse/YARN-3189
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Anushri
>Assignee: Anushri
>Priority: Minor
> Attachments: YARN-3189.patch, YARN-3189.patch, YARN-3189_1.patch
>
>
> Yarn application usage command should not give -appstate and -apptype since 
> these two are applicable to --list command..
>  *Can somebody please assign this issue to me* 



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


[jira] [Updated] (YARN-3189) Yarn application usage command should not give -appstate and -apptype

2015-03-17 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3189:
--
Attachment: YARN-3189.patch

> Yarn application usage command should not give -appstate and -apptype
> -
>
> Key: YARN-3189
> URL: https://issues.apache.org/jira/browse/YARN-3189
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Anushri
>Assignee: Anushri
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: YARN-3189.patch, YARN-3189.patch
>
>
> Yarn application usage command should not give -appstate and -apptype since 
> these two are applicable to --list command..
>  *Can somebody please assign this issue to me* 



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


[jira] [Updated] (YARN-3189) Yarn application usage command should not give -appstate and -apptype

2015-03-17 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3189:
--
Fix Version/s: 3.0.0

> Yarn application usage command should not give -appstate and -apptype
> -
>
> Key: YARN-3189
> URL: https://issues.apache.org/jira/browse/YARN-3189
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Anushri
>Assignee: Anushri
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: YARN-3189.patch
>
>
> Yarn application usage command should not give -appstate and -apptype since 
> these two are applicable to --list command..
>  *Can somebody please assign this issue to me* 



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


[jira] [Updated] (YARN-3189) Yarn application usage command should not give -appstate and -apptype

2015-02-26 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3189:
--
Attachment: YARN-3189.patch

> Yarn application usage command should not give -appstate and -apptype
> -
>
> Key: YARN-3189
> URL: https://issues.apache.org/jira/browse/YARN-3189
> Project: Hadoop YARN
>  Issue Type: Bug
>Affects Versions: 2.6.0
>Reporter: Anushri
>Assignee: Anushri
>Priority: Minor
> Attachments: YARN-3189.patch
>
>
> Yarn application usage command should not give -appstate and -apptype since 
> these two are applicable to --list command..
>  *Can somebody please assign this issue to me* 



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


[jira] [Commented] (YARN-3188) yarn application --list should list all the applications ( Not only submitted,accepted and running)

2015-02-12 Thread Anushri (JIRA)

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

Anushri commented on YARN-3188:
---

As far as i opine at the very first view when a user goes for " yarn 
application -list " command he will expect all the applications to be listed. 
Moreover the description of list command doesn't  specify it.

Also we have option to filter out from the list, so on a view level we are 
trying to filter out the objects from a list  that are not present there.

> yarn application --list should list all the applications ( Not only 
> submitted,accepted and running)
> ---
>
> Key: YARN-3188
> URL: https://issues.apache.org/jira/browse/YARN-3188
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: applications, client
>Reporter: Anushri
>Assignee: Anushri
>Priority: Minor
>
> By default yarn application --list should list all the applications since we 
> are not giving -appstate option.
> Currently it is giving like following..
> {noformat}
> [hdfs@host194 bin]$ ./yarn application -list
> 15/02/12 19:33:02 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 15/02/12 19:33:03 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Total number of applications (application-types: [] and states: [SUBMITTED, 
> ACCEPTED, RUNNING]):1
> Application-Id  Application-NameApplication-Type  
> User   Queue   State Final-State  
>ProgressTracking-URL
> application_1422888408992_15010  grep-search   MAPREDUCE  
> hdfs defaultACCEPTED   UNDEFINED  
>  0% N/A
> [
> {noformat}
> *Can somebody please assign this issue to me..?* 



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


[jira] [Created] (YARN-3189) Yarn application usage command should not give -appstate and -apptype

2015-02-12 Thread Anushri (JIRA)
Anushri created YARN-3189:
-

 Summary: Yarn application usage command should not give -appstate 
and -apptype
 Key: YARN-3189
 URL: https://issues.apache.org/jira/browse/YARN-3189
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.6.0
Reporter: Anushri
Priority: Minor


Yarn application usage command should not give -appstate and -apptype since 
these two are applicable to --list command..


 *Can somebody please assign this issue to me* 



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


[jira] [Updated] (YARN-3188) yarn application --list should list all the applications ( Not only submitted,accepted and running)

2015-02-12 Thread Anushri (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anushri updated YARN-3188:
--
Description: 
By default yarn application --list should list all the applications since we 
are not giving -appstate option.

Currently it is giving like following..
{noformat}
[hdfs@host194 bin]$ ./yarn application -list
15/02/12 19:33:02 INFO client.RMProxy: Connecting to ResourceManager at 
/0.0.0.0:8032
15/02/12 19:33:03 WARN util.NativeCodeLoader: Unable to load native-hadoop 
library for your platform... using builtin-java classes where applicable
Total number of applications (application-types: [] and states: [SUBMITTED, 
ACCEPTED, RUNNING]):1
Application-Id  Application-NameApplication-Type
  User   Queue   State Final-State  
   ProgressTracking-URL
application_1422888408992_15010  grep-search   MAPREDUCE
  hdfs defaultACCEPTED   UNDEFINED  
 0% N/A
[
{noformat}


*Can somebody please assign this issue to me..?* 

  was:
By default yarn application --list should list all the applications since we 
are not giving -appstate option.

{noformat}
[hdfs@host194 bin]$ ./yarn application -list
15/02/12 19:33:02 INFO client.RMProxy: Connecting to ResourceManager at 
/0.0.0.0:8032
15/02/12 19:33:03 WARN util.NativeCodeLoader: Unable to load native-hadoop 
library for your platform... using builtin-java classes where applicable
Total number of applications (application-types: [] and states: [SUBMITTED, 
ACCEPTED, RUNNING]):1
Application-Id  Application-NameApplication-Type
  User   Queue   State Final-State  
   ProgressTracking-URL
application_1422888408992_15010  grep-search   MAPREDUCE
  hdfs defaultACCEPTED   UNDEFINED  
 0% N/A
[
{noformat}


*Can somebody please assign this issue to me..?* 


> yarn application --list should list all the applications ( Not only 
> submitted,accepted and running)
> ---
>
> Key: YARN-3188
> URL: https://issues.apache.org/jira/browse/YARN-3188
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: applications, client
>Reporter: Anushri
>Priority: Minor
>
> By default yarn application --list should list all the applications since we 
> are not giving -appstate option.
> Currently it is giving like following..
> {noformat}
> [hdfs@host194 bin]$ ./yarn application -list
> 15/02/12 19:33:02 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:8032
> 15/02/12 19:33:03 WARN util.NativeCodeLoader: Unable to load native-hadoop 
> library for your platform... using builtin-java classes where applicable
> Total number of applications (application-types: [] and states: [SUBMITTED, 
> ACCEPTED, RUNNING]):1
> Application-Id  Application-NameApplication-Type  
> User   Queue   State Final-State  
>ProgressTracking-URL
> application_1422888408992_15010  grep-search   MAPREDUCE  
> hdfs defaultACCEPTED   UNDEFINED  
>  0% N/A
> [
> {noformat}
> *Can somebody please assign this issue to me..?* 



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


[jira] [Created] (YARN-3188) yarn application --list should list all the applications ( Not only submitted,accepted and running)

2015-02-12 Thread Anushri (JIRA)
Anushri created YARN-3188:
-

 Summary: yarn application --list should list all the applications 
( Not only submitted,accepted and running)
 Key: YARN-3188
 URL: https://issues.apache.org/jira/browse/YARN-3188
 Project: Hadoop YARN
  Issue Type: Bug
  Components: applications, client
Reporter: Anushri
Priority: Minor


By default yarn application --list should list all the applications since we 
are not giving -appstate option.

{noformat}
[hdfs@host194 bin]$ ./yarn application -list
15/02/12 19:33:02 INFO client.RMProxy: Connecting to ResourceManager at 
/0.0.0.0:8032
15/02/12 19:33:03 WARN util.NativeCodeLoader: Unable to load native-hadoop 
library for your platform... using builtin-java classes where applicable
Total number of applications (application-types: [] and states: [SUBMITTED, 
ACCEPTED, RUNNING]):1
Application-Id  Application-NameApplication-Type
  User   Queue   State Final-State  
   ProgressTracking-URL
application_1422888408992_15010  grep-search   MAPREDUCE
  hdfs defaultACCEPTED   UNDEFINED  
 0% N/A
[
{noformat}


*Can somebody please assign this issue to me..?* 



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