[jira] [Created] (YARN-4009) CORS support for ResourceManager REST API
Prakash Ramachandran created YARN-4009: -- Summary: CORS support for ResourceManager REST API Key: YARN-4009 URL: https://issues.apache.org/jira/browse/YARN-4009 Project: Hadoop YARN Issue Type: Bug Reporter: Prakash Ramachandran Currently the REST API's do not have CORS support. This means any UI (running in browser) cannot consume the REST API's. For ex Tez UI would like to use the REST API for getting application, application attempt information exposed by the API's. It would be very useful if CORS is enabled for the REST API's. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3148) allow CORS related headers to passthrough in WebAppProxyServlet
[ https://issues.apache.org/jira/browse/YARN-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534440#comment-14534440 ] Prakash Ramachandran commented on YARN-3148: [~varun_saxena] just to clarify. I believe the header filtering does not happen for the response headers. is that right? > allow CORS related headers to passthrough in WebAppProxyServlet > --- > > Key: YARN-3148 > URL: https://issues.apache.org/jira/browse/YARN-3148 > Project: Hadoop YARN > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Prakash Ramachandran >Assignee: Varun Saxena > Labels: BB2015-05-RFC > Attachments: YARN-3148.001.patch, YARN-3148.02.patch > > > currently the WebAppProxyServlet filters the request headers as defined by > passThroughHeaders. Tez UI is building a webapp which using rest api to fetch > data from the am via the rm tracking url. > for this purpose it would be nice to have additional headers allowed > especially the ones related to CORS. A few of them that would help are > * Origin > * Access-Control-Request-Method > * Access-Control-Request-Headers -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3530) ATS throws exception on trying to filter results without otherinfo.
[
https://issues.apache.org/jira/browse/YARN-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514204#comment-14514204
]
Prakash Ramachandran commented on YARN-3530:
LGTM.
> ATS throws exception on trying to filter results without otherinfo.
> ---
>
> Key: YARN-3530
> URL: https://issues.apache.org/jira/browse/YARN-3530
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Sreenath Somarajapuram
>Assignee: Zhijie Shen
>Priority: Critical
> Attachments: YARN-3530.1.patch
>
>
> Scenario:
> Am attempting to make data loading faster by fetching otherinfo on demand. As
> shown in the attached image, the patch adds a 'Load Counters' checkbox. It
> would be disabled by default, and on clicking, the counter data also would be
> loaded.
> Issue:
> Things are good when otherinfo is loaded.
> But ATS throws exception on trying to filter on status or applicationId
> without otherinfo in fields list.
> In other words, using fields=events,primaryfilters with
> secondaryFilter=status:RUNNING will return
> { "exception": "WebApplicationException", "message":
> "java.lang.NullPointerException", "javaClassName":
> "javax.ws.rs.WebApplicationException" }
> from the server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records
[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345366#comment-14345366 ] Prakash Ramachandran commented on YARN-3267: [~lichangleo] I am not very familiar with the yarn code, I can test the patch though. > Timelineserver applies the ACL rules after applying the limit on the number > of records > -- > > Key: YARN-3267 > URL: https://issues.apache.org/jira/browse/YARN-3267 > Project: Hadoop YARN > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Prakash Ramachandran >Assignee: Chang Li > Attachments: YARN_3267_WIP.patch, YARN_3267_WIP1.patch, > YARN_3267_WIP2.patch > > > While fetching the entities from timelineserver, the limit is applied on the > entities to be fetched from leveldb, the ACL filters are applied after this > (TimelineDataManager.java::getEntities). > this could mean that even if there are entities available which match the > query criteria, we could end up not getting any results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3268) timelineserver rest api returns html page for 404 when a bad endpoint is used.
Prakash Ramachandran created YARN-3268: -- Summary: timelineserver rest api returns html page for 404 when a bad endpoint is used. Key: YARN-3268 URL: https://issues.apache.org/jira/browse/YARN-3268 Project: Hadoop YARN Issue Type: Bug Reporter: Prakash Ramachandran the timelineserver returns a 404 page instead of giving a REST response. this interferes with the end user pages which try to retrieve data using REST api. this could be due to lack of a 404 handler ex. http://timelineserver:8188/badnamespace/v1/timeline/someentity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records
Prakash Ramachandran created YARN-3267: -- Summary: Timelineserver applies the ACL rules after applying the limit on the number of records Key: YARN-3267 URL: https://issues.apache.org/jira/browse/YARN-3267 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.6.0 Reporter: Prakash Ramachandran While fetching the entities from timelineserver, the limit is applied on the entities to be fetched from leveldb, the ACL filters are applied after this (TimelineDataManager.java::getEntities). this could mean that even if there are entities available which match the query criteria, we could end up not getting any results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3207) secondary filter matches entites which do not have the key being filtered for.
Prakash Ramachandran created YARN-3207:
--
Summary: secondary filter matches entites which do not have the
key being filtered for.
Key: YARN-3207
URL: https://issues.apache.org/jira/browse/YARN-3207
Project: Hadoop YARN
Issue Type: Bug
Components: timelineserver
Reporter: Prakash Ramachandran
in the leveldb implementation of the TimelineStore the secondary filter matches
entities where the key being searched for is not present.
ex query from tez ui
http://uvm:8188/ws/v1/timeline/TEZ_DAG_ID/?limit=1&secondaryFilter=foo:bar
will match and return the entity even though there is no entity with
otherinfo.foo defined.
the issue seems to be in
{code:title=LeveldbTimelineStore:675}
if (vs != null && !vs.contains(filter.getValue())) {
filterPassed = false;
break;
}
{code}
this should be IMHO
vs == null || !vs.contains(filter.getValue())
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (YARN-3148) allow CORS related headers to passthrough in WebAppProxyServlet
Prakash Ramachandran created YARN-3148: -- Summary: allow CORS related headers to passthrough in WebAppProxyServlet Key: YARN-3148 URL: https://issues.apache.org/jira/browse/YARN-3148 Project: Hadoop YARN Issue Type: Improvement Reporter: Prakash Ramachandran currently the WebAppProxyServlet filters the request headers as defined by passThroughHeaders. Tez UI is building a webapp which using rest api to fetch data from the am via the rm tracking url. for this purpose it would be nice to have additional headers allowed especially the ones related to CORS. A few of them that would help are * Origin * Access-Control-Request-Method * Access-Control-Request-Headers -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-3062) timelineserver gives inconsistent data for otherinfo field based on the filter param
[
https://issues.apache.org/jira/browse/YARN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278878#comment-14278878
]
Prakash Ramachandran commented on YARN-3062:
[~zjshen] looks like that was the issue. can close this jira now. Thanks
> timelineserver gives inconsistent data for otherinfo field based on the
> filter param
>
>
> Key: YARN-3062
> URL: https://issues.apache.org/jira/browse/YARN-3062
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Affects Versions: 2.4.0, 2.5.0, 2.6.0
>Reporter: Prakash Ramachandran
> Attachments: withfilter.json, withoutfilter.json
>
>
> When otherinfo field gets updated, in some cases the data returned for an
> entity is dependent on the filter usage.
> for ex in the attached files for the
> - entity: "vertex_1421164610335_0020_1_01",
> - entitytype: "TEZ_VERTEX_ID",
> for the otherinfo.numTasks, got updated from 1009 to 253
> - using
> {code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
> {code} gives the updated value: 253
> - using
> {code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
> gives the old value: 1009
>
> for the otherinfo.status field, which gets updated, both of them show the
> updated value.
> TEZ-1942 has more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (YARN-3062) timelineserver gives inconsistent data for otherinfo field based on the filter param
[
https://issues.apache.org/jira/browse/YARN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277573#comment-14277573
]
Prakash Ramachandran commented on YARN-3062:
thanks for the clarification.[~zjshen] could be the reason, will check and
update.
so to clarify
* if I have 2 primaryFilters while creating the entity, any update to entity
has to use the TimelineEntity.addPrimaryFilter for both primaryFilters?
* can a new primaryfilter be added in an update. (2 primaryfilters at entity
creation time, add a new filter in update to make 3 filters, every subsequent
update sets all 3 filters)
* can the primaryFilter value be changed in an update?
> timelineserver gives inconsistent data for otherinfo field based on the
> filter param
>
>
> Key: YARN-3062
> URL: https://issues.apache.org/jira/browse/YARN-3062
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Affects Versions: 2.4.0, 2.5.0, 2.6.0
>Reporter: Prakash Ramachandran
> Attachments: withfilter.json, withoutfilter.json
>
>
> When otherinfo field gets updated, in some cases the data returned for an
> entity is dependent on the filter usage.
> for ex in the attached files for the
> - entity: "vertex_1421164610335_0020_1_01",
> - entitytype: "TEZ_VERTEX_ID",
> for the otherinfo.numTasks, got updated from 1009 to 253
> - using
> {code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
> {code} gives the updated value: 253
> - using
> {code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
> gives the old value: 1009
>
> for the otherinfo.status field, which gets updated, both of them show the
> updated value.
> TEZ-1942 has more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3062) timelineserver gives inconsistent data for otherinfo field based on the filter param
[
https://issues.apache.org/jira/browse/YARN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prakash Ramachandran updated YARN-3062:
---
Description:
When otherinfo field gets updated, in some cases the data returned for an
entity is dependent on the filter usage.
for ex in the attached files for the
- entity: "vertex_1421164610335_0020_1_01",
- entitytype: "TEZ_VERTEX_ID",
for the otherinfo.numTasks, got updated from 1009 to 253
- using
{code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
{code} gives the updated value: 253
- using
{code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
gives the old value: 1009
for the otherinfo.status field, which gets updated, both of them show the
updated value.
TEZ-1942 has more details.
was:
When otherinfo field gets updated, in some cases the data returned for an
entity is dependent on the filter usage.
for ex in the attached files for the
- entity: "vertex_1421164610335_0020_1_01",
- entitytype: "TEZ_VERTEX_ID",
for the otherinfo.numTasks, got updated from 1009 to 253
- using
{code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
{code} gives the updated value: 1009
- using
{code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
gives the old value: 253
for the otherinfo.status field, which gets updated, both of them show the
updated value.
TEZ-1942 has more details.
> timelineserver gives inconsistent data for otherinfo field based on the
> filter param
>
>
> Key: YARN-3062
> URL: https://issues.apache.org/jira/browse/YARN-3062
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Prakash Ramachandran
> Attachments: withfilter.json, withoutfilter.json
>
>
> When otherinfo field gets updated, in some cases the data returned for an
> entity is dependent on the filter usage.
> for ex in the attached files for the
> - entity: "vertex_1421164610335_0020_1_01",
> - entitytype: "TEZ_VERTEX_ID",
> for the otherinfo.numTasks, got updated from 1009 to 253
> - using
> {code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
> {code} gives the updated value: 253
> - using
> {code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
> gives the old value: 1009
>
> for the otherinfo.status field, which gets updated, both of them show the
> updated value.
> TEZ-1942 has more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3062) timelineserver gives inconsistent data for otherinfo field based on the filter param
[
https://issues.apache.org/jira/browse/YARN-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prakash Ramachandran updated YARN-3062:
---
Attachment: withoutfilter.json
withfilter.json
attaching sample output files.
> timelineserver gives inconsistent data for otherinfo field based on the
> filter param
>
>
> Key: YARN-3062
> URL: https://issues.apache.org/jira/browse/YARN-3062
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
>Reporter: Prakash Ramachandran
> Attachments: withfilter.json, withoutfilter.json
>
>
> When otherinfo field gets updated, in some cases the data returned for an
> entity is dependent on the filter usage.
> for ex in the attached files for the
> - entity: "vertex_1421164610335_0020_1_01",
> - entitytype: "TEZ_VERTEX_ID",
> for the otherinfo.numTasks, got updated from 1009 to 253
> - using
> {code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
> {code} gives the updated value: 1009
> - using
> {code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
> gives the old value: 253
>
> for the otherinfo.status field, which gets updated, both of them show the
> updated value.
> TEZ-1942 has more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (YARN-3062) timelineserver gives inconsistent data for otherinfo field based on the filter param
Prakash Ramachandran created YARN-3062:
--
Summary: timelineserver gives inconsistent data for otherinfo
field based on the filter param
Key: YARN-3062
URL: https://issues.apache.org/jira/browse/YARN-3062
Project: Hadoop YARN
Issue Type: Bug
Components: timelineserver
Reporter: Prakash Ramachandran
When otherinfo field gets updated, in some cases the data returned for an
entity is dependent on the filter usage.
for ex in the attached files for the
- entity: "vertex_1421164610335_0020_1_01",
- entitytype: "TEZ_VERTEX_ID",
for the otherinfo.numTasks, got updated from 1009 to 253
- using
{code}http://machine:8188/ws/v1/timeline/TEZ_VERTEX_ID/vertex_1421164610335_0020_1_01/
{code} gives the updated value: 1009
- using
{code}http://cn042-10:8188/ws/v1/timeline/TEZ_VERTEX_ID?limit=11&primaryFilter=TEZ_DAG_ID%3Adag_1421164610335_0020_1{code}
gives the old value: 253
for the otherinfo.status field, which gets updated, both of them show the
updated value.
TEZ-1942 has more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (YARN-2968) yarn shell script has unresolved merge conflicts in checkin
Prakash Ramachandran created YARN-2968: -- Summary: yarn shell script has unresolved merge conflicts in checkin Key: YARN-2968 URL: https://issues.apache.org/jira/browse/YARN-2968 Project: Hadoop YARN Issue Type: Bug Reporter: Prakash Ramachandran in the branch-2 yarn command has unresolved merge conflicts https://github.com/apache/hadoop/blob/branch-2/hadoop-yarn-project/hadoop-yarn/bin/yarn commit - aadd0c392be66080f see line 203, 106 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-2525) yarn logs command gives error on trunk
Prakash Ramachandran created YARN-2525: -- Summary: yarn logs command gives error on trunk Key: YARN-2525 URL: https://issues.apache.org/jira/browse/YARN-2525 Project: Hadoop YARN Issue Type: Bug Reporter: Prakash Ramachandran Priority: Minor yarn logs command (trunk branch) gives an error Error: Could not find or load main class org.apache.hadoop.yarn.logaggregation.LogDumper instead the class should be org.apache.hadoop.yarn.client.cli.LogsCLI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
