[jira] [Updated] (YARN-5011) Support metric filters for flow runs

[ https://issues.apache.org/jira/browse/YARN-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5011: - Parent Issue: YARN-7055 (was: YARN-5355) > Support metric filters for flow runs >

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-5094: - Parent Issue: YARN-7055 (was: YARN-5355) > some YARN container events have timestamp of -1 >

[jira] [Updated] (YARN-5357) Timeline service v2 integration with Federation

[ https://issues.apache.org/jira/browse/YARN-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5357: - Parent Issue: YARN-7055 (was: YARN-5355) > Timeline service v2 integration with Federation >

[jira] [Updated] (YARN-5260) Review / Recommendations for hbase writer code

[ https://issues.apache.org/jira/browse/YARN-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5260: - Parent Issue: YARN-7055 (was: YARN-5355) > Review / Recommendations for hbase writer code >

[jira] [Updated] (YARN-5071) address HBase compatibility issues with trunk

[ https://issues.apache.org/jira/browse/YARN-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5071: - Parent Issue: YARN-7055 (was: YARN-5355) > address HBase compatibility issues with trunk >

[jira] [Updated] (YARN-4821) Have a separate NM timeline publishing-interval

[ https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-4821: - Parent Issue: YARN-7055 (was: YARN-5355) > Have a separate NM timeline publishing-interval >

[jira] [Created] (YARN-7055) YARN Timeline Service v.2: beta 1

Vrushali C created YARN-7055: Summary: YARN Timeline Service v.2: beta 1 Key: YARN-7055 URL: https://issues.apache.org/jira/browse/YARN-7055 Project: Hadoop YARN Issue Type: New Feature

[jira] [Updated] (YARN-5336) Put in some limit for accepting key-values in hbase writer

[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5336: - Parent Issue: YARN-7055 (was: YARN-5355) > Put in some limit for accepting key-values in hbase writer >

[jira] [Updated] (YARN-3874) Optimize and synchronize FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3874: - Parent Issue: YARN-7055 (was: YARN-5355) > Optimize and synchronize FS Reader and Writer Implementations

[jira] [Updated] (YARN-3872) TimelineReader Web UI Implementation

[ https://issues.apache.org/jira/browse/YARN-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3872: - Parent Issue: YARN-7055 (was: YARN-5355) > TimelineReader Web UI Implementation >

[jira] [Updated] (YARN-3841) [Storage implementation] Adding retry semantics to HDFS backing storage

[ https://issues.apache.org/jira/browse/YARN-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3841: - Parent Issue: YARN-7055 (was: YARN-5355) > [Storage implementation] Adding retry semantics to HDFS

[jira] [Updated] (YARN-3865) Backward compatibility of reader with ATSv1

[ https://issues.apache.org/jira/browse/YARN-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3865: - Parent Issue: YARN-7055 (was: YARN-5355) > Backward compatibility of reader with ATSv1 >

[jira] [Updated] (YARN-3822) Scalability validation of RM writing app/attempt/container lifecycle events

[ https://issues.apache.org/jira/browse/YARN-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3822: - Parent Issue: YARN-7055 (was: YARN-5355) > Scalability validation of RM writing app/attempt/container

[jira] [Updated] (YARN-3818) [Aggregation] Queue-level Aggregation on Application States table

[ https://issues.apache.org/jira/browse/YARN-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3818: - Parent Issue: YARN-7055 (was: YARN-5355) > [Aggregation] Queue-level Aggregation on Application States

[jira] [Updated] (YARN-7036) [ATSv2] : NPE for recovered finished applications in NM during upgrade

[ https://issues.apache.org/jira/browse/YARN-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-7036: - Parent Issue: YARN-7055 (was: YARN-5355) > [ATSv2] : NPE for recovered finished applications in NM during

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-6767: - Parent Issue: YARN-7055 (was: YARN-5355) > Timeline client won't be able to write when TimelineCollector

[jira] [Updated] (YARN-6931) Make the aggregation interval in AppLevelTimelineCollector configurable

[ https://issues.apache.org/jira/browse/YARN-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6931: - Parent Issue: YARN-7055 (was: YARN-5355) > Make the aggregation interval in AppLevelTimelineCollector

[jira] [Updated] (YARN-6904) [ATSv2] Fix findbugs warnings

[ https://issues.apache.org/jira/browse/YARN-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6904: - Parent Issue: YARN-7055 (was: YARN-5355) > [ATSv2] Fix findbugs warnings > -

[jira] [Updated] (YARN-6989) Ensure timeline service v2 codebase gets UGI from HttpServletRequest in a consistent way

[ https://issues.apache.org/jira/browse/YARN-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6989: - Parent Issue: YARN-7055 (was: YARN-5355) > Ensure timeline service v2 codebase gets UGI from

[jira] [Updated] (YARN-3488) AM get timeline service info from RM rather than Application specific configuration.

[ https://issues.apache.org/jira/browse/YARN-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3488: - Parent Issue: YARN-7055 (was: YARN-5355) > AM get timeline service info from RM rather than Application

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-3545: - Parent Issue: YARN-7055 (was: YARN-5355) > Investigate the concurrency issue with the map of timeline

[jira] [Updated] (YARN-3352) [Event producers] Change distributed shell to use TIMELINE_SERVICE_VERSION

[ https://issues.apache.org/jira/browse/YARN-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3352: - Parent Issue: YARN-7055 (was: YARN-5355) > [Event producers] Change distributed shell to use

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

[ https://issues.apache.org/jira/browse/YARN-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3509: - Parent Issue: YARN-7055 (was: YARN-5355) > CollectorNodemanagerProtocol's authorization doesn't work >

[jira] [Updated] (YARN-3166) [Source organization] Decide detailed package structures for timeline service v2 components

[ https://issues.apache.org/jira/browse/YARN-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3166: - Parent Issue: YARN-7055 (was: YARN-5355) > [Source organization] Decide detailed package structures for

[jira] [Updated] (YARN-3401) [Security] users should not be able to create a generic TimelineEntity and associate arbitrary type

[ https://issues.apache.org/jira/browse/YARN-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3401: - Parent Issue: YARN-7055 (was: YARN-5355) > [Security] users should not be able to create a generic

[jira] [Updated] (YARN-3588) Timeline entity uniqueness

[ https://issues.apache.org/jira/browse/YARN-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3588: - Parent Issue: YARN-7055 (was: YARN-5355) > Timeline entity uniqueness > -- > >

[jira] [Updated] (YARN-3622) Enable application client to communicate with new timeline service

[ https://issues.apache.org/jira/browse/YARN-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3622: - Parent Issue: YARN-7055 (was: YARN-5355) > Enable application client to communicate with new timeline

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

[ https://issues.apache.org/jira/browse/YARN-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6047: - Parent Issue: YARN-7055 (was: YARN-5355) > Documentation updates for TimelineService v2 >

[jira] [Updated] (YARN-6063) Inline java doc with Hadoop formatter

[ https://issues.apache.org/jira/browse/YARN-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6063: - Parent Issue: YARN-7055 (was: YARN-5355) > Inline java doc with Hadoop formatter >

[jira] [Updated] (YARN-6121) Launch app collectors for unmanaged AMs'

[ https://issues.apache.org/jira/browse/YARN-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6121: - Parent Issue: YARN-7055 (was: YARN-5355) > Launch app collectors for unmanaged AMs' >

[jira] [Updated] (YARN-6105) Support for new REST end point /clusterids

[ https://issues.apache.org/jira/browse/YARN-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6105: - Parent Issue: YARN-7055 (was: YARN-5355) > Support for new REST end point /clusterids >

[jira] [Updated] (YARN-5751) Support UNIT for TimelineMetric

[ https://issues.apache.org/jira/browse/YARN-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5751: - Parent Issue: YARN-7055 (was: YARN-5355) > Support UNIT for TimelineMetric >

[jira] [Updated] (YARN-6058) Support for listing all applications i.e /apps

[ https://issues.apache.org/jira/browse/YARN-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6058: - Parent Issue: YARN-7055 (was: YARN-5355) > Support for listing all applications i.e /apps >

[jira] [Updated] (YARN-5760) [ATSv2] Create HBase connection only if an app collector is publishing from NM

[ https://issues.apache.org/jira/browse/YARN-5760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5760: - Parent Issue: YARN-7055 (was: YARN-5355) > [ATSv2] Create HBase connection only if an app collector is

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-5681: - Parent Issue: YARN-7055 (was: YARN-5355) > Change collector discovery to support collectors mapped to

[jira] [Updated] (YARN-5981) Coprocessor related code changes/cleanup pending HBASE-17273

[ https://issues.apache.org/jira/browse/YARN-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5981: - Parent Issue: YARN-7055 (was: YARN-5355) > Coprocessor related code changes/cleanup pending HBASE-17273 >

[jira] [Updated] (YARN-5742) Serve aggregated logs of historical apps from timeline service

[ https://issues.apache.org/jira/browse/YARN-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5742: - Parent Issue: YARN-7055 (was: YARN-5355) > Serve aggregated logs of historical apps from timeline service

[jira] [Updated] (YARN-6699) [ATSv2 Security] Delegation token support for Timeline reader

[ https://issues.apache.org/jira/browse/YARN-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6699: - Parent Issue: YARN-7055 (was: YARN-5355) > [ATSv2 Security] Delegation token support for Timeline reader

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

[ https://issues.apache.org/jira/browse/YARN-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6047: - Parent Issue: YARN-5355 (was: YARN-7055) > Documentation updates for TimelineService v2 >

[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-YARN-5355.0002.patch Uploading v002 as per Haibo's recommendation > Rolling

[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-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] [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-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-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=16003476#comment-16003476 ] Vrushali C commented on YARN-6559: -- Huh, interesting. Naga does mention that he has committed to YARN-5355

[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-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] [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-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] [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-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-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] [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] [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-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-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] [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] [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] [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] [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] [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] [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] [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-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-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-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=16025452#comment-16025452 ] Vrushali C commented on YARN-6555: -- No more comments, patch looks good. +1. [~haibo.chen] please feel

[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-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-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-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] [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-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-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-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] [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-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] [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-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] [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] [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-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] [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] [Assigned] (YARN-7188) TimelineSchemaCreator fails to create flowrun table

[ https://issues.apache.org/jira/browse/YARN-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-7188: Assignee: Vrushali C > TimelineSchemaCreator fails to create flowrun table >

[jira] [Commented] (YARN-7188) TimelineSchemaCreator fails to create flowrun table

[ https://issues.apache.org/jira/browse/YARN-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16164880#comment-16164880 ] Vrushali C commented on YARN-7188: -- The coprocessor jar was earlier picked up from the classpath since it

[jira] [Created] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

Vrushali C created YARN-7190: Summary: Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath Key: YARN-7190 URL: https://issues.apache.org/jira/browse/YARN-7190 Project:

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167129#comment-16167129 ] Vrushali C commented on YARN-7190: -- Hi [~jlowe] Were you referring to HADOOP-12857 for the hadoop-tools

[jira] [Updated] (YARN-7169) Backport new yarn-ui to branch2 code (starting with YARN-5355_branch2)

[ https://issues.apache.org/jira/browse/YARN-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-7169: - Summary: Backport new yarn-ui to branch2 code (starting with YARN-5355_branch2) (was: Backport new

[jira] [Updated] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-7190: - Target Version/s: 2.9.0 Description: [~jlowe] had a good observation about the user classpath

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206156#comment-16206156 ] Vrushali C commented on YARN-7190: -- Should also go into trunk I think. > Ensure only NM classpath in 2.x

<    5   6   7   8   9   10   11   12   13   14   >