[
https://issues.apache.org/jira/browse/YARN-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681723#comment-13681723
]
Arpit Gupta commented on YARN-800:
--
Here is the stack trace
{code}
HTTP ERROR 500
Problem
[
https://issues.apache.org/jira/browse/YARN-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681727#comment-13681727
]
Arpit Gupta commented on YARN-800:
--
Looks like we have to set the property
[
https://issues.apache.org/jira/browse/YARN-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta reassigned YARN-673:
Assignee: Arpit Gupta
Remove yarn-default.xml
---
Key:
Arpit Gupta created YARN-845:
Summary: RM crash with NPE on NODE_UPDATE
Key: YARN-845
URL: https://issues.apache.org/jira/browse/YARN-845
Project: Hadoop YARN
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/YARN-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685988#comment-13685988
]
Arpit Gupta commented on YARN-845:
--
Mayank
Unfortunately cannot consistently reproduce
[
https://issues.apache.org/jira/browse/YARN-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-845:
-
Description:
the following stack trace is generated in rm
{code}
n, service: 68.142.246.147:45454 }, ]
[
https://issues.apache.org/jira/browse/YARN-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-845:
-
Attachment: rm.log
rm log attached
RM crash with NPE on NODE_UPDATE
[
https://issues.apache.org/jira/browse/YARN-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-800:
-
Priority: Minor (was: Critical)
Clicking on an AM link for a running app leads to a HTTP 500
[
https://issues.apache.org/jira/browse/YARN-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-845:
-
Description:
the following stack trace is generated in rm
{code}
n, service: 68.142.246.147:45454 }, ]
[
https://issues.apache.org/jira/browse/YARN-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13686196#comment-13686196
]
Arpit Gupta commented on YARN-800:
--
Changing it to minor. If i set
Arpit Gupta created YARN-1082:
-
Summary: Secure RM with recovery enabled and rm state store on
hdfs fails with gss exception
Key: YARN-1082
URL: https://issues.apache.org/jira/browse/YARN-1082
Project:
[
https://issues.apache.org/jira/browse/YARN-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744121#comment-13744121
]
Arpit Gupta commented on YARN-1082:
---
Here are the logs
{code}
2013-08-17 17:32:08,272
[
https://issues.apache.org/jira/browse/YARN-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13744154#comment-13744154
]
Arpit Gupta commented on YARN-1082:
---
It looks like we try to interact with hdfs before
[
https://issues.apache.org/jira/browse/YARN-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750337#comment-13750337
]
Arpit Gupta commented on YARN-1097:
---
For example here is a small snippet of the client
Arpit Gupta created YARN-1102:
-
Summary: YARN-1074 added the ability to filter by multiple
application states but the YARN webservice does not have the same feature
Key: YARN-1102
URL:
[
https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751435#comment-13751435
]
Arpit Gupta commented on YARN-1102:
---
I also noticed that the value in state is case
[
https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751460#comment-13751460
]
Arpit Gupta commented on YARN-1102:
---
[~zjshen]
Thanks. Should i log another jira for
Arpit Gupta created YARN-1103:
-
Summary: Make finalStatus, user, queue, application types and
states case insensitive in yarn webservices
Key: YARN-1103
URL: https://issues.apache.org/jira/browse/YARN-1103
[
https://issues.apache.org/jira/browse/YARN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta resolved YARN-1102.
---
Resolution: Duplicate
YARN-1074 added the ability to filter by multiple application states but
[
https://issues.apache.org/jira/browse/YARN-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1103:
--
Issue Type: Improvement (was: Bug)
Make finalStatus, user, queue, application types and states
Arpit Gupta created YARN-1107:
-
Summary: Restart secure RM with recovery enabled while oozie jobs
are running causes the RM to fail during startup
Key: YARN-1107
URL: https://issues.apache.org/jira/browse/YARN-1107
[
https://issues.apache.org/jira/browse/YARN-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1107:
--
Attachment: rm.log
Attached the rm log
Restart secure RM with recovery enabled while
Arpit Gupta created YARN-1220:
-
Summary: Yarn RM fs state store should handle safemode exceptions
Key: YARN-1220
URL: https://issues.apache.org/jira/browse/YARN-1220
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1220:
--
Summary: Yarn App recovers when it should not as delete failed from rm fs
store (was: Yarn RM fs state
Arpit Gupta created YARN-2563:
-
Summary: On secure clusters call to timeline server fails with
authentication errors when running a job via oozie
Key: YARN-2563
URL: https://issues.apache.org/jira/browse/YARN-2563
[
https://issues.apache.org/jira/browse/YARN-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14136486#comment-14136486
]
Arpit Gupta commented on YARN-2563:
---
Here is the stack trace
{code}
ozie-oozi-W@wc]
Arpit Gupta created YARN-1783:
-
Summary: yarn application does not make any progress even when no
other application is running when RM is being restarted in the background
Key: YARN-1783
URL:
[
https://issues.apache.org/jira/browse/YARN-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920105#comment-13920105
]
Arpit Gupta commented on YARN-1783:
---
application that took the longest is
[
https://issues.apache.org/jira/browse/YARN-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1783:
--
Description:
Noticed that during HA tests some tests took over 3 hours to run when the test
failed.
[
https://issues.apache.org/jira/browse/YARN-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1800:
--
Environment: (was: HDP 2.0)
YARN NodeManager with java.util.concurrent.RejectedExecutionException
Arpit Gupta created YARN-1816:
-
Summary: Succeeded application remains in accepted state causing
the tests to hang
Key: YARN-1816
URL: https://issues.apache.org/jira/browse/YARN-1816
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1816:
--
Summary: Succeeded application remains in accepted (was: Succeeded
application remains in accepted
Arpit Gupta created YARN-1827:
-
Summary: yarn client fails when RM is killed within 5s of job
submission
Key: YARN-1827
URL: https://issues.apache.org/jira/browse/YARN-1827
Project: Hadoop YARN
Arpit Gupta created YARN-1861:
-
Summary: Both RM stuck in standby mode when automatic failover is
enabled
Key: YARN-1861
URL: https://issues.apache.org/jira/browse/YARN-1861
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13942554#comment-13942554
]
Arpit Gupta commented on YARN-1861:
---
Here is a snippet from the log
{code}
2014-03-18
[
https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13942624#comment-13942624
]
Arpit Gupta commented on YARN-1861:
---
It was stuck for a while hard to determine the time
Arpit Gupta created YARN-1866:
-
Summary: YARN RM fails to load state store with delegation token
parsing error
Key: YARN-1866
URL: https://issues.apache.org/jira/browse/YARN-1866
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13945613#comment-13945613
]
Arpit Gupta commented on YARN-1866:
---
{code}
interface
Arpit Gupta created YARN-1878:
-
Summary: Yarn standby RM taking long to transition to active
Key: YARN-1878
URL: https://issues.apache.org/jira/browse/YARN-1878
Project: Hadoop YARN
Issue Type:
[
https://issues.apache.org/jira/browse/YARN-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13947513#comment-13947513
]
Arpit Gupta commented on YARN-1878:
---
In comparison HDFS Namenode usually can transition
Arpit Gupta created YARN-1885:
-
Summary: yarn logs command does not provide the application logs
for some applications
Key: YARN-1885
URL: https://issues.apache.org/jira/browse/YARN-1885
Project: Hadoop
Arpit Gupta created YARN-1886:
-
Summary: Exceptions in the RM log while cleaning up app attempt
Key: YARN-1886
URL: https://issues.apache.org/jira/browse/YARN-1886
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950027#comment-13950027
]
Arpit Gupta commented on YARN-1886:
---
{code}
2014-03-27 10:20:24,728 INFO
[
https://issues.apache.org/jira/browse/YARN-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1886:
--
Description:
Noticed exceptions in the RM log while HA tests were running where we killed
[
https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13950976#comment-13950976
]
Arpit Gupta commented on YARN-1885:
---
yarn logs -applicationId returned nothing. And the
[
https://issues.apache.org/jira/browse/YARN-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965886#comment-13965886
]
Arpit Gupta commented on YARN-1924:
---
Here is the stack trace.
{code}
cheduler from user
Arpit Gupta created YARN-1924:
-
Summary: RM shut down with RMFatalEvent of type
STATE_STORE_OP_FAILED
Key: YARN-1924
URL: https://issues.apache.org/jira/browse/YARN-1924
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1246:
--
Assignee: Jian He
Log application status in the rm log when app is done running
Arpit Gupta created YARN-1246:
-
Summary: Log application status in the rm log when app is done
running
Key: YARN-1246
URL: https://issues.apache.org/jira/browse/YARN-1246
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta reassigned YARN-1246:
-
Assignee: Arpit Gupta (was: Jian He)
Log application status in the rm log when app is done
[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1246:
--
Affects Version/s: 2.1.1-beta
Log application status in the rm log when app is done running
[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1246:
--
Attachment: YARN-1246.patch
Log application status in the rm log when app is done running
[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780536#comment-13780536
]
Arpit Gupta commented on YARN-1246:
---
With the patch we get the following log
{code}
[
https://issues.apache.org/jira/browse/YARN-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780577#comment-13780577
]
Arpit Gupta commented on YARN-1246:
---
No tests added as this is a minor change to a log
Arpit Gupta created YARN-1252:
-
Summary: Secure RM fails to start up in secure HA setup with
Renewal request for unknown token exception
Key: YARN-1252
URL: https://issues.apache.org/jira/browse/YARN-1252
Arpit Gupta created YARN-1255:
-
Summary: RM fails to start up with Failed to load/recover state
error in a HA setup
Key: YARN-1255
URL: https://issues.apache.org/jira/browse/YARN-1255
Project: Hadoop
[
https://issues.apache.org/jira/browse/YARN-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta resolved YARN-1255.
---
Resolution: Duplicate
Thanks [~jlowe] it is.
RM fails to start up with Failed to load/recover state
[
https://issues.apache.org/jira/browse/YARN-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13782363#comment-13782363
]
Arpit Gupta commented on YARN-1185:
---
Here is the stack trace from the RM when it tries to
[
https://issues.apache.org/jira/browse/YARN-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13795418#comment-13795418
]
Arpit Gupta commented on YARN-1308:
---
I think we should set the defaults to
{code}
Arpit Gupta created YARN-1308:
-
Summary: set default value for nodemanager aux service
Key: YARN-1308
URL: https://issues.apache.org/jira/browse/YARN-1308
Project: Hadoop YARN
Issue Type: Bug
[
https://issues.apache.org/jira/browse/YARN-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796235#comment-13796235
]
Arpit Gupta commented on YARN-1308:
---
[~hitesh]
Confirmed when
[
https://issues.apache.org/jira/browse/YARN-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta resolved YARN-1319.
---
Resolution: Duplicate
Documentation has wrong entry
--
[
https://issues.apache.org/jira/browse/YARN-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848122#comment-13848122
]
Arpit Gupta commented on YARN-1459:
---
Another thing that would help users is we could
Arpit Gupta created YARN-1639:
-
Summary: YARM RM HA requires different configs on different RM
hosts
Key: YARN-1639
URL: https://issues.apache.org/jira/browse/YARN-1639
Project: Hadoop YARN
Arpit Gupta created YARN-1660:
-
Summary: add the ability to set
yarn.resourcemanager.hostname.rm-id instead of setting all the various
host:port properties for RM
Key: YARN-1660
URL:
[
https://issues.apache.org/jira/browse/YARN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883658#comment-13883658
]
Arpit Gupta commented on YARN-1660:
---
Here is a list of properties that one needs to set
[
https://issues.apache.org/jira/browse/YARN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1660:
--
Assignee: Xuan Gong
add the ability to set yarn.resourcemanager.hostname.rm-id instead of setting
[
https://issues.apache.org/jira/browse/YARN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884758#comment-13884758
]
Arpit Gupta commented on YARN-1660:
---
nope yarn-site should only have
{code}
property
[
https://issues.apache.org/jira/browse/YARN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884776#comment-13884776
]
Arpit Gupta commented on YARN-1660:
---
The way it works in non HA mode is that
Arpit Gupta created YARN-1665:
-
Summary: Set better defaults for HA configs
Key: YARN-1665
URL: https://issues.apache.org/jira/browse/YARN-1665
Project: Hadoop YARN
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/YARN-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Gupta updated YARN-1665:
--
Summary: Set better defaults for HA configs for automatic failover (was:
Set better defaults for HA
Arpit Gupta created YARN-2743:
-
Summary: Yarn jobs via oozie fail with failed to renew token
(secure) or digest mismatch (unsecure) errors when RM is being killed
Key: YARN-2743
URL:
[
https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183902#comment-14183902
]
Arpit Gupta commented on YARN-2743:
---
Here is the stack trace from un secure run
{code}
[
https://issues.apache.org/jira/browse/YARN-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183899#comment-14183899
]
Arpit Gupta commented on YARN-2743:
---
Here is the stack trace from a secure run
{code}
Arpit Gupta created YARN-2805:
-
Summary: RM2 in HA setup tries to login using the RM1's kerberos
principal
Key: YARN-2805
URL: https://issues.apache.org/jira/browse/YARN-2805
Project: Hadoop YARN
Arpit Gupta created YARN-3178:
-
Summary: Clean up stack trace on the client when RM fails over
Key: YARN-3178
URL: https://issues.apache.org/jira/browse/YARN-3178
Project: Hadoop YARN
Issue
[
https://issues.apache.org/jira/browse/YARN-3178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317034#comment-14317034
]
Arpit Gupta commented on YARN-3178:
---
Here is an example stack trace
{code}
14/02/25
77 matches
Mail list logo
