[jira] [Commented] (YARN-4455) Support fetching metrics by time range

[ https://issues.apache.org/jira/browse/YARN-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094254#comment-16094254 ] Vrushali C commented on YARN-4455: -- Yes, thanks [~varun_impala_149e] and [~rohithsharma]. filed YARN-6850

[jira] [Created] (YARN-6850) Ensure that supplemented timestamp is stored only for flow run metrics

Vrushali C created YARN-6850: Summary: Ensure that supplemented timestamp is stored only for flow run metrics Key: YARN-6850 URL: https://issues.apache.org/jira/browse/YARN-6850 Project: Hadoop YARN

[jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094243#comment-16094243 ] Vrushali C commented on YARN-6820: -- Adding to what I mentioned above. If a user’s labels do not match a

[jira] [Comment Edited] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094234#comment-16094234 ] Vrushali C edited comment on YARN-6820 at 7/20/17 5:59 AM: --- Thinking out loud:

[jira] [Commented] (YARN-4455) Support fetching metrics by time range

[ https://issues.apache.org/jira/browse/YARN-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094237#comment-16094237 ] Vrushali C commented on YARN-4455: -- bq. From above discussion I understand that only flow run entity table

[jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094234#comment-16094234 ] Vrushali C commented on YARN-6820: -- Thinking out loud: Wondering if we can make use HBase visibility

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094183#comment-16094183 ] Vrushali C commented on YARN-6733: -- bq. Btw, as discussion made in YARN-4455 regarding timestamp

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094167#comment-16094167 ] Vrushali C commented on YARN-6733: -- Gentle ping for review [~rohithsharma] [~varun_saxena] I have made all

[jira] [Commented] (YARN-4455) Support fetching metrics by time range

[ https://issues.apache.org/jira/browse/YARN-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091847#comment-16091847 ] Vrushali C commented on YARN-4455: -- Yes, I know we have functions to read the supplemented timestamp...

[jira] [Commented] (YARN-6767) Timeline client won't be able to write when TimelineCollector is not up yet, or NM is down

[ https://issues.apache.org/jira/browse/YARN-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091187#comment-16091187 ] Vrushali C commented on YARN-6767: -- Here is my observation in one case. I started up a job and then killed

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.005.patch Attaching v005 that updates the documentation info > Add table

[jira] [Commented] (YARN-4455) Support fetching metrics by time range

[ https://issues.apache.org/jira/browse/YARN-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090796#comment-16090796 ] Vrushali C commented on YARN-4455: -- Yes, thanks for the patch [~varun_saxena]! bq. Primarily used to

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090257#comment-16090257 ] Vrushali C commented on YARN-6733: -- bq. can you update subapplication row and column schema java doc.

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.004.patch Attaching v004 to fix checkstyle comments. > Add table for

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.003.patch Uploading v003 with the actual user id at the end of the row

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086576#comment-16086576 ] Vrushali C commented on YARN-6733: -- hey [~rohithsharma] So I remembered why we wanted to put in the

[jira] [Commented] (YARN-3895) Support ACLs in ATSv2

[ https://issues.apache.org/jira/browse/YARN-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086424#comment-16086424 ] Vrushali C commented on YARN-3895: -- Filed YARN-6820 for adding in a basic read size restriction. >

[jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086420#comment-16086420 ] Vrushali C commented on YARN-6820: -- YARN-3895 will add support for ACLs. I am expecting this jira

[jira] [Updated] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6820: - Labels: yarn-5355-merge-blocker (was: ) > Restrict read access to timelineservice v2 data >

[jira] [Created] (YARN-6820) Restrict read access to timelineservice v2 data

Vrushali C created YARN-6820: Summary: Restrict read access to timelineservice v2 data Key: YARN-6820 URL: https://issues.apache.org/jira/browse/YARN-6820 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.002.patch > Add table for storing sub-application entities >

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: (was: YARN-6733-YARN-5355.002.patch) > Add table for storing sub-application entities >

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.002.patch Uploading patch v002. Modified the row key to be subAppUserId !

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085251#comment-16085251 ] Vrushali C commented on YARN-6733: -- bq. But for adhoc queries, adding whole query into row key does not

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085222#comment-16085222 ] Vrushali C commented on YARN-6733: -- [~rohithsharma] I have been thinking over this again. I think I will

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085210#comment-16085210 ] Vrushali C commented on YARN-6733: -- bq. Unlike entity table schema, if user is the preference across

[jira] [Commented] (YARN-6555) Store application flow context in NM state store for work-preserving restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084801#comment-16084801 ] Vrushali C commented on YARN-6555: -- One question I have now is, should we bump up the NM State store

[jira] [Commented] (YARN-5681) Change collector discovery to support collectors mapped to clients but not applications

[ https://issues.apache.org/jira/browse/YARN-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16084448#comment-16084448 ] Vrushali C commented on YARN-5681: -- Hi [~gtCarrera9] Would you be working on this? Or is it okay if

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: IMG_7040.JPG > Add table for storing sub-application entities >

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082810#comment-16082810 ] Vrushali C commented on YARN-6733: -- bq. I do not remember why subAppName was added!!? Can you remind me?

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081813#comment-16081813 ] Vrushali C commented on YARN-6733: -- Will address the checkstyle issues along with any other review

[jira] [Commented] (YARN-6801) NPE in RM while setting collectors map in NodeHeartbeatResponse

[ https://issues.apache.org/jira/browse/YARN-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081761#comment-16081761 ] Vrushali C commented on YARN-6801: -- It's interesting, it's not during the upgrade. It's when there are

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: (was: YARN-6733-YARN-5355.001.patch) > Add table for storing sub-application entities >

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.001.patch > Add table for storing sub-application entities >

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Attachment: YARN-6733-YARN-5355.001.patch Attaching v001. - added a new package

[jira] [Updated] (YARN-6801) NPE in RM while setting collectors map in NodeHeartbeatResponse

[ https://issues.apache.org/jira/browse/YARN-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6801: - Attachment: YARN-6801-YARN-5355.001.patch Attaching v001 > NPE in RM while setting collectors map in

[jira] [Created] (YARN-6801) NPE in RM while setting collectors map in NodeHeartbeatResponse

Vrushali C created YARN-6801: Summary: NPE in RM while setting collectors map in NodeHeartbeatResponse Key: YARN-6801 URL: https://issues.apache.org/jira/browse/YARN-6801 Project: Hadoop YARN

[jira] [Commented] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061301#comment-16061301 ] Vrushali C commented on YARN-6733: -- Hi [~haibo.chen], Good questions. Let me try to answer them and give

[jira] [Created] (YARN-6736) Consider writing to both ats v1 & v2 from RM for smoother upgrades

Vrushali C created YARN-6736: Summary: Consider writing to both ats v1 & v2 from RM for smoother upgrades Key: YARN-6736 URL: https://issues.apache.org/jira/browse/YARN-6736 Project: Hadoop YARN

[jira] [Created] (YARN-6735) Have a way to turn off system metrics from NMs

Vrushali C created YARN-6735: Summary: Have a way to turn off system metrics from NMs Key: YARN-6735 URL: https://issues.apache.org/jira/browse/YARN-6735 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-6734) Ensure sub-application user is extracted & sent to timeline service

Vrushali C created YARN-6734: Summary: Ensure sub-application user is extracted & sent to timeline service Key: YARN-6734 URL: https://issues.apache.org/jira/browse/YARN-6734 Project: Hadoop YARN

[jira] [Updated] (YARN-6733) Add table for storing sub-application entities

[ https://issues.apache.org/jira/browse/YARN-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6733: - Summary: Add table for storing sub-application entities (was: Support storing sub-application entities)

[jira] [Created] (YARN-6733) Support storing sub-application entities

Vrushali C created YARN-6733: Summary: Support storing sub-application entities Key: YARN-6733 URL: https://issues.apache.org/jira/browse/YARN-6733 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-6047) Documentation updates for TimelineService v2

[ https://issues.apache.org/jira/browse/YARN-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058787#comment-16058787 ] Vrushali C commented on YARN-6047: -- +1 to Haibo's note about possibility of data loss in certain

[jira] [Commented] (YARN-6047) Documentation updates for TimelineService v2

[ https://issues.apache.org/jira/browse/YARN-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054768#comment-16054768 ] Vrushali C commented on YARN-6047: -- Thanks [~rohithsharma]. I also noticed that we don't have much

[jira] [Commented] (YARN-6707) [ATSv2] Update HBase version to 1.2.6

[ https://issues.apache.org/jira/browse/YARN-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045239#comment-16045239 ] Vrushali C commented on YARN-6707: -- Alright, it looks like trunk and YARN-5355-branch-2 also work with

[jira] [Updated] (YARN-6707) [ATSv2] Update HBase version to 1.2.6

[ https://issues.apache.org/jira/browse/YARN-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6707: - Attachment: YARN-6707-YARN-5355.001.patch Looks like this needs just the version change. I have done this

[jira] [Commented] (YARN-6707) [ATSv2] Update HBase version to 1.2.6

[ https://issues.apache.org/jira/browse/YARN-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045165#comment-16045165 ] Vrushali C commented on YARN-6707: -- Looking into this. > [ATSv2] Update HBase version to 1.2.6 >

[jira] [Assigned] (YARN-6707) [ATSv2] Update HBase version to 1.2.6

[ https://issues.apache.org/jira/browse/YARN-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-6707: Assignee: Vrushali C > [ATSv2] Update HBase version to 1.2.6 >

[jira] [Commented] (YARN-5094) some YARN container events have timestamp of -1

[ https://issues.apache.org/jira/browse/YARN-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035296#comment-16035296 ] Vrushali C commented on YARN-5094: -- Thanks [~haibochen] for the patch. Do you think we might want to put

[jira] [Commented] (YARN-6316) Provide help information and documentation for TimelineSchemaCreator

[ https://issues.apache.org/jira/browse/YARN-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033929#comment-16033929 ] Vrushali C commented on YARN-6316: -- I have pushed to YARN-5355, now pushing to YARN-5355-branch-2 as well.

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033183#comment-16033183 ] Vrushali C commented on YARN-6323: -- Hmm, using the same thing for flow name at both RM and NM does sound

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032023#comment-16032023 ] Vrushali C commented on YARN-6323: -- Hmm, I have been thinking over this and I think we all discussed a bit

[jira] [Commented] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025452#comment-16025452 ] Vrushali C commented on YARN-6555: -- No more comments, patch looks good. +1. [~haibo.chen] please feel

[jira] [Commented] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023859#comment-16023859 ] Vrushali C commented on YARN-6555: -- Thanks Rohith and Haibo for the patch and discussions. I think I

[jira] [Commented] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022046#comment-16022046 ] Vrushali C commented on YARN-6555: -- Thanks for picking this up Rohith, I will take a look at the patch and

[jira] [Commented] (YARN-6316) Provide help information and documentation for TimelineSchemaCreator

[ https://issues.apache.org/jira/browse/YARN-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022044#comment-16022044 ] Vrushali C commented on YARN-6316: -- Thanks [~haibo.chen]! The patch 00 looks good. I will wait for a day

[jira] [Commented] (YARN-6047) Documentation updates for TimelineService v2

[ https://issues.apache.org/jira/browse/YARN-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022043#comment-16022043 ] Vrushali C commented on YARN-6047: -- Thanks [~rohithsharma] for the patch. I am wondering if we might want

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16011130#comment-16011130 ] Vrushali C commented on YARN-6323: -- Thanks [~haibochen] for the review! Yes, you are right, we do want to

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008676#comment-16008676 ] Vrushali C commented on YARN-6323: -- The NM Findbug warnings are unrelated to the patch. > Rolling

[jira] [Assigned] (YARN-6580) Incorrect logger for FairSharePolicy

[ https://issues.apache.org/jira/browse/YARN-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-6580: Assignee: Vrushali C > Incorrect logger for FairSharePolicy >

[jira] [Updated] (YARN-6580) Incorrect logger for FairSharePolicy

[ https://issues.apache.org/jira/browse/YARN-6580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6580: - Attachment: YARN-6580.001.patch Attaching patch 001. > Incorrect logger for FairSharePolicy >

[jira] [Updated] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6323: - Attachment: YARN-6323.001.patch Uploading patch 001. This patch adds in a default flow context when the

[jira] [Commented] (YARN-6316) Provide help information and documentation for TimelineSchemaCreator

[ https://issues.apache.org/jira/browse/YARN-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16008411#comment-16008411 ] Vrushali C commented on YARN-6316: -- Thanks [~haibochen] for the patch. 1) Could we also update the

[jira] [Commented] (YARN-3981) offline collector: support timeline clients not associated with an application

[ https://issues.apache.org/jira/browse/YARN-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005775#comment-16005775 ] Vrushali C commented on YARN-3981: -- Thanks for the design draft Rohith. I think I have some preliminary

[jira] [Commented] (YARN-6564) RM service is shutting down when ATS v2 is enabled

[ https://issues.apache.org/jira/browse/YARN-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004041#comment-16004041 ] Vrushali C commented on YARN-6564: -- I think this jira can be closed as "Not a problem"? > RM service is

[jira] [Assigned] (YARN-6435) [ATSv2] Can't retrieve more than 1000 versions of metrics in time series

[ https://issues.apache.org/jira/browse/YARN-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-6435: Assignee: Vrushali C (was: Rohith Sharma K S) > [ATSv2] Can't retrieve more than 1000 versions of

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003803#comment-16003803 ] Vrushali C commented on YARN-6323: -- bq. However, in the upgrade path, we could choose to not write

[jira] [Commented] (YARN-3545) Investigate the concurrency issue with the map of timeline collector

[ https://issues.apache.org/jira/browse/YARN-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003581#comment-16003581 ] Vrushali C commented on YARN-3545: -- Hmm, I think we thought the patch was stale even then and decided to

[jira] [Commented] (YARN-6559) Findbugs warning in YARN-5355 branch

[ https://issues.apache.org/jira/browse/YARN-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003476#comment-16003476 ] Vrushali C commented on YARN-6559: -- Huh, interesting. Naga does mention that he has committed to YARN-5355

[jira] [Commented] (YARN-6563) ConcurrentModificationException in TimelineCollectorManager while stopping RM

[ https://issues.apache.org/jira/browse/YARN-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003191#comment-16003191 ] Vrushali C commented on YARN-6563: -- + 1 LGTM Will commit it shortly. > ConcurrentModificationException

[jira] [Commented] (YARN-6559) Findbugs warning in YARN-5355 branch

[ https://issues.apache.org/jira/browse/YARN-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003127#comment-16003127 ] Vrushali C commented on YARN-6559: -- Yes, that output is confusing. Looking at the console output

[jira] [Commented] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001633#comment-16001633 ] Vrushali C commented on YARN-6555: -- Thanks [~haibochen], I will use that jira YARN-6323 for ensuring a

[jira] [Commented] (YARN-6564) RM service is shutting down when ATS v2 is enabled

[ https://issues.apache.org/jira/browse/YARN-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16000962#comment-16000962 ] Vrushali C commented on YARN-6564: -- Trunk is being rolled back to guava 11 HADOOP-14386 > RM service is

[jira] [Commented] (YARN-6566) add a property for a hadoop job to identified which hive HQL submitted by which one in multi-users environment

[ https://issues.apache.org/jira/browse/YARN-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999544#comment-15999544 ] Vrushali C commented on YARN-6566: -- Yes, with our project hRaven at twitter

[jira] [Commented] (YARN-6563) ConcurrentModificationException in TimelineCollectorManager while stopping RM

[ https://issues.apache.org/jira/browse/YARN-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15999258#comment-15999258 ] Vrushali C commented on YARN-6563: -- Did you notice this on trunk? I did not see it yet with the backported

[jira] [Commented] (YARN-6564) RM service is shutting down when ATS v2 is enabled

[ https://issues.apache.org/jira/browse/YARN-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998497#comment-15998497 ] Vrushali C commented on YARN-6564: -- Related jira which makes guava version configurable HADOOP-14380 > RM

[jira] [Commented] (YARN-6564) RM service is shutting down when ATS v2 is enabled

[ https://issues.apache.org/jira/browse/YARN-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998493#comment-15998493 ] Vrushali C commented on YARN-6564: -- Thanks Rohith and Akhil, we will have to look into this. > RM

[jira] [Updated] (YARN-6375) App level aggregation should not consider metric values reported in the previous aggregation cycle

[ https://issues.apache.org/jira/browse/YARN-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6375: - Hadoop Flags: Reviewed > App level aggregation should not consider metric values reported in the >

[jira] [Updated] (YARN-6375) App level aggregation should not consider metric values reported in the previous aggregation cycle

[ https://issues.apache.org/jira/browse/YARN-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6375: - Target Version/s: 3.0.0-alpha3 > App level aggregation should not consider metric values reported in the

[jira] [Commented] (YARN-6375) App level aggregation should not consider metric values reported in the previous aggregation cycle

[ https://issues.apache.org/jira/browse/YARN-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15997521#comment-15997521 ] Vrushali C commented on YARN-6375: -- Thanks [~varun_saxena] for the 002 patch. LGTM, I will commit it

[jira] [Updated] (YARN-6561) Update exception information during timeline collector aux service initialization

[ https://issues.apache.org/jira/browse/YARN-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6561: - Attachment: YARN-6561.001.patch Uploading patch v001 > Update exception information during timeline

[jira] [Created] (YARN-6561) Update exception information during timeline collector aux service initialization

Vrushali C created YARN-6561: Summary: Update exception information during timeline collector aux service initialization Key: YARN-6561 URL: https://issues.apache.org/jira/browse/YARN-6561 Project:

[jira] [Updated] (YARN-3981) offline collector: support timeline clients not associated with an application

[ https://issues.apache.org/jira/browse/YARN-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3981: - Summary: offline collector: support timeline clients not associated with an application (was: support

[jira] [Assigned] (YARN-6559) Findbugs warning in YARN-5355 branch

[ https://issues.apache.org/jira/browse/YARN-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-6559: Assignee: Vrushali C > Findbugs warning in YARN-5355 branch >

[jira] [Updated] (YARN-6559) Findbugs warning in YARN-5355 branch

[ https://issues.apache.org/jira/browse/YARN-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6559: - Attachment: YARN-6559-YARN-5355.001.patch Attaching patch 001 > Findbugs warning in YARN-5355 branch >

[jira] [Commented] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996925#comment-15996925 ] Vrushali C commented on YARN-6555: -- I am seeing this in our code that's backported to branch-2 (2.6 with

[jira] [Commented] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995963#comment-15995963 ] Vrushali C commented on YARN-6555: -- In the case that there isn't a prior flow context, we also want to

[jira] [Updated] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

[ https://issues.apache.org/jira/browse/YARN-6555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6555: - Description: If timeline service v2 is enabled and NM is restarted with recovery enabled, then NM fails

[jira] [Created] (YARN-6555) Enable flow context read (& corresponding write) for recovering application with NM restart

Vrushali C created YARN-6555: Summary: Enable flow context read (& corresponding write) for recovering application with NM restart Key: YARN-6555 URL: https://issues.apache.org/jira/browse/YARN-6555

[jira] [Commented] (YARN-6375) App level aggregation should not consider metric values reported in the previous aggregation cycle

[ https://issues.apache.org/jira/browse/YARN-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989521#comment-15989521 ] Vrushali C commented on YARN-6375: -- Hi [~varun_saxena] I noticed some checkstyle issues in the new test

[jira] [Commented] (YARN-6534) ResourceManager failed due to TimelineClient try to init SSLFactory even https is not enabled

[ https://issues.apache.org/jira/browse/YARN-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987325#comment-15987325 ] Vrushali C commented on YARN-6534: -- Got it, thanks [~djp], please go ahead. > ResourceManager failed due

[jira] [Commented] (YARN-6375) App level aggregation should not consider metric values reported in the previous aggregation cycle

[ https://issues.apache.org/jira/browse/YARN-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987166#comment-15987166 ] Vrushali C commented on YARN-6375: -- +1 Thanks [~varun_saxena] for the patch. Yes, I think we would need

[jira] [Commented] (YARN-6534) ResourceManager failed due to TimelineClient try to init SSLFactory even https is not enabled

[ https://issues.apache.org/jira/browse/YARN-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987159#comment-15987159 ] Vrushali C commented on YARN-6534: -- +1 Patch looks good. Thanks [~rohithsharma] An extremely minor

[jira] [Updated] (YARN-6534) ResourceManager failed due to TimelineClient try to init SSLFactory even https is not enabled

[ https://issues.apache.org/jira/browse/YARN-6534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6534: - Labels: yarn-5355-merge-blocker (was: ) > ResourceManager failed due to TimelineClient try to init

[jira] [Commented] (YARN-3509) CollectorNodemanagerProtocol's authorization doesn't work

[ https://issues.apache.org/jira/browse/YARN-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967762#comment-15967762 ] Vrushali C commented on YARN-3509: -- cc [~varun_saxena] for security jiras >

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959365#comment-15959365 ] Vrushali C commented on YARN-6323: -- We would like to fix this so that we can deploy atsv2 without

[jira] [Assigned] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-6323: Assignee: Vrushali C > Rolling upgrade/config change is broken on timeline v2. >

[jira] [Commented] (YARN-6435) [ATSv2] Can't retrieve more than 1000 versions of metrics in time series

[ https://issues.apache.org/jira/browse/YARN-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955723#comment-15955723 ] Vrushali C commented on YARN-6435: -- Yes, the 1000 was put in as a default to restrict the number of values

[jira] [Commented] (YARN-6424) TimelineCollector is not stopped when an app finishes in RM

[ https://issues.apache.org/jira/browse/YARN-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15953990#comment-15953990 ] Vrushali C commented on YARN-6424: -- Thanks [~varun_saxena]. No, we don't need to make more changes. Let's

<    2   3   4   5   6   7   8   9   10   11   >