[jira] [Commented] (YARN-5755) Enhancements to STOP queue handling

[ https://issues.apache.org/jira/browse/YARN-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15590010#comment-15590010 ] Vrushali C commented on YARN-5755: -- Could you add a bit more detail as to what is meant by

[jira] [Updated] (YARN-3649) Allow configurable prefix for hbase table names (like prod, exp, test etc)

[ https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3649: - Attachment: YARN-3649-YARN-5355.003.patch Uploading patch v3. Included the new test file and modified the d

[jira] [Assigned] (YARN-5686) DefaultContainerExecutor random working dir algorigthm skews results

[ https://issues.apache.org/jira/browse/YARN-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-5686: Assignee: Vrushali C > DefaultContainerExecutor random working dir algorigthm skews results > --

[jira] [Updated] (YARN-5686) DefaultContainerExecutor random working dir algorigthm skews results

[ https://issues.apache.org/jira/browse/YARN-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5686: - Attachment: YARN-5686.001.patch Uploading patch v001. Also added unit tests for checking the example case

[jira] [Updated] (YARN-3649) Allow configurable prefix for hbase table names (like prod, exp, test etc)

[ https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3649: - Attachment: YARN-3649-YARN-5355.004.patch Alright, one more attempt at fixing the checkstyle issues > All

[jira] [Commented] (YARN-5686) DefaultContainerExecutor random working dir algorigthm skews results

[ https://issues.apache.org/jira/browse/YARN-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592425#comment-15592425 ] Vrushali C commented on YARN-5686: -- Thanks [~miklos.szeg...@cloudera.com], yes will reorde

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15592684#comment-15592684 ] Vrushali C commented on YARN-5760: -- Yes, opening a connection (checking for an open connec

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15592693#comment-15592693 ] Vrushali C commented on YARN-5760: -- Also, a related thought is considering using node labe

[jira] [Updated] (YARN-5686) DefaultContainerExecutor random working dir algorigthm skews results

[ https://issues.apache.org/jira/browse/YARN-5686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5686: - Attachment: YARN-5686.002.patch Uploading patch 002 that reorders the test case data and fixes the checksty

[jira] [Commented] (YARN-5747) Application timeline metric aggregation in timeline v2 will lose last round aggregation when an application finishes

[ https://issues.apache.org/jira/browse/YARN-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592836#comment-15592836 ] Vrushali C commented on YARN-5747: -- LGTM too. > Application timeline metric aggregation

[jira] [Commented] (YARN-5755) Enhancements to STOP queue handling

[ https://issues.apache.org/jira/browse/YARN-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15593076#comment-15593076 ] Vrushali C commented on YARN-5755: -- I would like to work on this if you can give me some m

[jira] [Commented] (YARN-3649) Allow configurable prefix for hbase table names (like prod, exp, test etc)

[ https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606006#comment-15606006 ] Vrushali C commented on YARN-3649: -- Thanks Varun, making the changes, will upload a patch

[jira] [Commented] (YARN-4173) Ensure the final values for metrics/events are emitted/stored at APP completion time

[ https://issues.apache.org/jira/browse/YARN-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606017#comment-15606017 ] Vrushali C commented on YARN-4173: -- In YARN-5747, the final aggregation is being done expl

[jira] [Commented] (YARN-5739) Provide timeline reader API to list available timeline entity types for one application

[ https://issues.apache.org/jira/browse/YARN-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606036#comment-15606036 ] Vrushali C commented on YARN-5739: -- Actually, this is not that hard to do. It requires mak

[jira] [Updated] (YARN-3649) Allow configurable prefix for hbase table names (like prod, exp, test etc)

[ https://issues.apache.org/jira/browse/YARN-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3649: - Attachment: YARN-3649-YARN-5355.005.patch Uploading v5 that addresses Varun's suggestions. Diff between th

[jira] [Commented] (YARN-5739) Provide timeline reader API to list available timeline entity types for one application

[ https://issues.apache.org/jira/browse/YARN-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606332#comment-15606332 ] Vrushali C commented on YARN-5739: -- So if we need only some entity types, then it's even e

[jira] [Assigned] (YARN-5780) [YARN native service] Allowing YARN native services to post data to timeline service V.2

[ https://issues.apache.org/jira/browse/YARN-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-5780: Assignee: Vrushali C > [YARN native service] Allowing YARN native services to post data to timeline

[jira] [Commented] (YARN-5780) [YARN native service] Allowing YARN native services to post data to timeline service V.2

[ https://issues.apache.org/jira/browse/YARN-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607406#comment-15607406 ] Vrushali C commented on YARN-5780: -- [~gtCarrera9] let me see if I can take a stab at this.

[jira] [Commented] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612891#comment-15612891 ] Vrushali C commented on YARN-1945: -- Patch looks good, it needs to be rebased again I think

[jira] [Assigned] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-1945: Assignee: Vrushali C (was: Siqi Li) > Adding description for each pool in Fair Scheduler Page from

[jira] [Comment Edited] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612891#comment-15612891 ] Vrushali C edited comment on YARN-1945 at 10/27/16 7:24 PM: Pat

[jira] [Commented] (YARN-3359) Recover collector list in RM failed over

[ https://issues.apache.org/jira/browse/YARN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612938#comment-15612938 ] Vrushali C commented on YARN-3359: -- [~gtCarrera9] , overall patch looks fine. Do you have

[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: - Labels: YARN-5355 oct16-medium (was: YARN-5355) > Investigate the concurrency issue with the map of timeli

[jira] [Updated] (YARN-3359) Recover collector list in RM failed over

[ https://issues.apache.org/jira/browse/YARN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3359: - Labels: YARN-5355 oct16-medium (was: YARN-5355) > Recover collector list in RM failed over > -

[jira] [Created] (YARN-5790) Address collector life-cycle/persistency issues on the NM side.

Vrushali C created YARN-5790: Summary: Address collector life-cycle/persistency issues on the NM side. Key: YARN-5790 URL: https://issues.apache.org/jira/browse/YARN-5790 Project: Hadoop YARN Is

[jira] [Commented] (YARN-3359) Recover collector list in RM failed over

[ https://issues.apache.org/jira/browse/YARN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612971#comment-15612971 ] Vrushali C commented on YARN-3359: -- Filed YARN-5790 for the NM side collector lifecycle co

[jira] [Commented] (YARN-5265) Make HBase configuration for the timeline service configurable

[ https://issues.apache.org/jira/browse/YARN-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613011#comment-15613011 ] Vrushali C commented on YARN-5265: -- Patch v9 looks good, will commit it in shortly on YARN

[jira] [Commented] (YARN-4765) Split TestHBaseTimelineStorage into multiple test classes

[ https://issues.apache.org/jira/browse/YARN-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613020#comment-15613020 ] Vrushali C commented on YARN-4765: -- Sounds good, will commit it in shortly. > Split TestH

[jira] [Commented] (YARN-4765) Split TestHBaseTimelineStorage into multiple test classes

[ https://issues.apache.org/jira/browse/YARN-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613255#comment-15613255 ] Vrushali C commented on YARN-4765: -- Most of the checkstyle warnings are about method lengt

[jira] [Commented] (YARN-4765) Split TestHBaseTimelineStorage into multiple test classes

[ https://issues.apache.org/jira/browse/YARN-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613325#comment-15613325 ] Vrushali C commented on YARN-4765: -- Committed to YARN-5355. {code} commit 513dcf6817dd76

[jira] [Commented] (YARN-4675) Reorganize TimeClientImpl into TimeClientV1Impl and TimeClientV2Impl

[ https://issues.apache.org/jira/browse/YARN-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613444#comment-15613444 ] Vrushali C commented on YARN-4675: -- Looked at this as part of the yarn meetup #4. I also d

[jira] [Updated] (YARN-4765) Split TestHBaseTimelineStorage into multiple test classes

[ https://issues.apache.org/jira/browse/YARN-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-4765: - Fix Version/s: YARN-5355 > Split TestHBaseTimelineStorage into multiple test classes >

[jira] [Resolved] (YARN-5790) Address collector life-cycle/persistency issues on the NM side.

[ https://issues.apache.org/jira/browse/YARN-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C resolved YARN-5790. -- Resolution: Duplicate Thanks [~varun_saxena], marking this closed as a duplicate of YARN-3115 > Address

[jira] [Commented] (YARN-3817) [Aggregation] Flow and User level aggregation on Application States table

[ https://issues.apache.org/jira/browse/YARN-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617548#comment-14617548 ] Vrushali C commented on YARN-3817: -- bq. This said, we may want to try to implement the of

[jira] [Commented] (YARN-3836) add equals and hashCode to TimelineEntity and other classes in the data model

[ https://issues.apache.org/jira/browse/YARN-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619145#comment-14619145 ] Vrushali C commented on YARN-3836: -- Hi [~gtCarrera] Sounds good, will reassign to you. t

[jira] [Updated] (YARN-3836) add equals and hashCode to TimelineEntity and other classes in the data model

[ https://issues.apache.org/jira/browse/YARN-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3836: - Assignee: Li Lu (was: Vrushali C) > add equals and hashCode to TimelineEntity and other classes in the dat

[jira] [Created] (YARN-3901) Populate flow run data in the flow_run table

Vrushali C created YARN-3901: Summary: Populate flow run data in the flow_run table Key: YARN-3901 URL: https://issues.apache.org/jira/browse/YARN-3901 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621571#comment-14621571 ] Vrushali C commented on YARN-3908: -- Hi [~zjshen] I see that event#info is not being store

[jira] [Updated] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3908: - Attachment: YARN-3908-YARN-2928.001.patch Hi [~zjshen], [~sjlee0], I have put together a quick patch tonigh

[jira] [Commented] (YARN-3949) ensure timely flush of timeline writes

[ https://issues.apache.org/jira/browse/YARN-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639251#comment-14639251 ] Vrushali C commented on YARN-3949: -- We are now setting the entityTable to null in the HBas

[jira] [Commented] (YARN-3949) ensure timely flush of timeline writes

[ https://issues.apache.org/jira/browse/YARN-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639391#comment-14639391 ] Vrushali C commented on YARN-3949: -- I think [~gtCarrera9] clarified my doubt.. thanks!

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641026#comment-14641026 ] Vrushali C commented on YARN-3908: -- Thanks everyone for the discussion. I will upload anot

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641211#comment-14641211 ] Vrushali C commented on YARN-3908: -- Sounds good, the current patch can be checked in and I

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643188#comment-14643188 ] Vrushali C commented on YARN-3908: -- Hi Zhijie Thanks.. that is a good point. But if we pu

[jira] [Commented] (YARN-3908) Bugs in HBaseTimelineWriterImpl

[ https://issues.apache.org/jira/browse/YARN-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643446#comment-14643446 ] Vrushali C commented on YARN-3908: -- Yes, let's get the current patch in and continue discu

[jira] [Commented] (YARN-3816) [Aggregation] App-level Aggregation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643463#comment-14643463 ] Vrushali C commented on YARN-3816: -- bq. If I understand the problem correctly, we have tw

[jira] [Commented] (YARN-3816) [Aggregation] App-level Aggregation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643729#comment-14643729 ] Vrushali C commented on YARN-3816: -- Yes, granularity of aggregation could drive the rollup

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643734#comment-14643734 ] Vrushali C commented on YARN-3904: -- bq. One thing pending discussion is about the aggreg

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643746#comment-14643746 ] Vrushali C commented on YARN-3984: -- Thanks for filing the jira [~zjshen]. The key design w

[jira] [Assigned] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-3984: Assignee: Vrushali C > Rethink event column key issue > -- > >

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643758#comment-14643758 ] Vrushali C commented on YARN-3984: -- I can take this up. Please feel free to reassign or if

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648428#comment-14648428 ] Vrushali C commented on YARN-3984: -- Hi Zhijie, bq. the current query we want to support n

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648491#comment-14648491 ] Vrushali C commented on YARN-3984: -- To reach a conclusion on this: If everyone/most folks

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648516#comment-14648516 ] Vrushali C commented on YARN-3984: -- If the query has the exact timestamp as well event id,

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648605#comment-14648605 ] Vrushali C commented on YARN-3984: -- Yes, right. Given an event id, in the case the column

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649584#comment-14649584 ] Vrushali C commented on YARN-3984: -- Great.. thanks.. bq. Secondly, how do we deal with a

[jira] [Commented] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649601#comment-14649601 ] Vrushali C commented on YARN-3984: -- bq. One question, do we make sure every event has such

[jira] [Updated] (YARN-3984) Rethink event column key issue

[ https://issues.apache.org/jira/browse/YARN-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3984: - Attachment: YARN-3984-YARN-2928.001.patch Attached patch v001 as per above discussions. One change is tha

[jira] [Resolved] (YARN-3167) [Collector implementation] Implement the core functionality of the timeline collector

[ https://issues.apache.org/jira/browse/YARN-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C resolved YARN-3167. -- Resolution: Invalid I think this jira is outdated now. The functionality of the Timeline Collector has

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660867#comment-14660867 ] Vrushali C commented on YARN-3049: -- Hi [~zjshen] In my experience, that kind of conversion

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660923#comment-14660923 ] Vrushali C commented on YARN-3049: -- It looks like the conversion back to String was done t

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660987#comment-14660987 ] Vrushali C commented on YARN-3049: -- Yes I will take that jira up. > [Storage Implementa

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660991#comment-14660991 ] Vrushali C commented on YARN-3049: -- bq. I'm worried that Bytes.toString() doesn't make the

[jira] [Created] (YARN-4025) Deal with byte representations of Longs in writer code

Vrushali C created YARN-4025: Summary: Deal with byte representations of Longs in writer code Key: YARN-4025 URL: https://issues.apache.org/jira/browse/YARN-4025 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3049) [Storage Implementation] Implement storage reader interface to fetch raw data from HBase backend

[ https://issues.apache.org/jira/browse/YARN-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661313#comment-14661313 ] Vrushali C commented on YARN-3049: -- Filed https://issues.apache.org/jira/browse/YARN-4025

[jira] [Commented] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662833#comment-14662833 ] Vrushali C commented on YARN-4025: -- The function {code} public Map readResults(Result resu

[jira] [Updated] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-4025: - Attachment: YARN-4025-YARN-2928.001.patch Attaching patch v001. I have updated the HBaseTimelineWriter to

[jira] [Commented] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680430#comment-14680430 ] Vrushali C commented on YARN-4025: -- Thanks [~sjlee0] and [~gtCarrera9] I will rebase and

[jira] [Commented] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692511#comment-14692511 ] Vrushali C commented on YARN-4025: -- Yes, +1 > Deal with byte representations of Longs in

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693931#comment-14693931 ] Vrushali C commented on YARN-3901: -- Am working on this. I have been discussing the details

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694055#comment-14694055 ] Vrushali C commented on YARN-3901: -- The application and entity tables support timeseries s

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694058#comment-14694058 ] Vrushali C commented on YARN-3901: -- For flows, users, queues which are aggregated on a ti

[jira] [Updated] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-4025: - Assignee: Sangjin Lee (was: Vrushali C) > Deal with byte representations of Longs in writer code > ---

[jira] [Commented] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694177#comment-14694177 ] Vrushali C commented on YARN-4025: -- Reassigning to Sangjin > Deal with byte representati

[jira] [Commented] (YARN-4053) Change the way metric values are stored in HBase Storage

[ https://issues.apache.org/jira/browse/YARN-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697500#comment-14697500 ] Vrushali C commented on YARN-4053: -- I think metric values should be stored (and read back)

[jira] [Commented] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697531#comment-14697531 ] Vrushali C commented on YARN-4025: -- Hmm, yes I think some more comments there might help (

[jira] [Commented] (YARN-4025) Deal with byte representations of Longs in writer code

[ https://issues.apache.org/jira/browse/YARN-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697534#comment-14697534 ] Vrushali C commented on YARN-4025: -- I changed it from '?' to '='. Sangjin was also wonder

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697537#comment-14697537 ] Vrushali C commented on YARN-3904: -- A very minor comment.. I think there is a typo in PHE

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697549#comment-14697549 ] Vrushali C commented on YARN-3904: -- A couple of more things that came to mind. We need not

[jira] [Commented] (YARN-4053) Change the way metric values are stored in HBase Storage

[ https://issues.apache.org/jira/browse/YARN-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697583#comment-14697583 ] Vrushali C commented on YARN-4053: -- Hmm good points. I think all metrics should be store

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697816#comment-14697816 ] Vrushali C commented on YARN-3904: -- +1 yes we can move ahead. I am quite curious, how is

[jira] [Updated] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: YARN-3901-YARN-2928.WIP.patch Uploading a work in progress patch. This patch is not yet rebase

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699978#comment-14699978 ] Vrushali C commented on YARN-3901: -- Thanks [~jrottinghuis] for looking into my wip patch.

[jira] [Commented] (YARN-3904) Refactor timelineservice.storage to add support to online and offline aggregation writers

[ https://issues.apache.org/jira/browse/YARN-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700250#comment-14700250 ] Vrushali C commented on YARN-3904: -- Thanks Li, latest patch looks good to me. > Refactor

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701775#comment-14701775 ] Vrushali C commented on YARN-3901: -- I see, yes, will name it accordingly. > Populate flo

[jira] [Updated] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: YARN-3901-YARN-2928.WIP.2.patch Updated WIP patch after discussion with [~jrottinghuis]. - ad

[jira] [Created] (YARN-4062) Add the coprocessor & scanner functionality for flow run table

Vrushali C created YARN-4062: Summary: Add the coprocessor & scanner functionality for flow run table Key: YARN-4062 URL: https://issues.apache.org/jira/browse/YARN-4062 Project: Hadoop YARN Iss

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703062#comment-14703062 ] Vrushali C commented on YARN-3901: -- Filed https://issues.apache.org/jira/browse/YARN-4062

[jira] [Assigned] (YARN-4063) Populate the flow activity table

[ https://issues.apache.org/jira/browse/YARN-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C reassigned YARN-4063: Assignee: Vrushali C > Populate the flow activity table > > >

[jira] [Created] (YARN-4063) Populate the flow activity table

Vrushali C created YARN-4063: Summary: Populate the flow activity table Key: YARN-4063 URL: https://issues.apache.org/jira/browse/YARN-4063 Project: Hadoop YARN Issue Type: Sub-task R

[jira] [Commented] (YARN-4063) Populate the flow activity table

[ https://issues.apache.org/jira/browse/YARN-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703541#comment-14703541 ] Vrushali C commented on YARN-4063: -- Current line of thinking - on application created and

[jira] [Created] (YARN-4069) For long running apps (> 2 days), populate flow activity table

Vrushali C created YARN-4069: Summary: For long running apps (> 2 days), populate flow activity table Key: YARN-4069 URL: https://issues.apache.org/jira/browse/YARN-4069 Project: Hadoop YARN Iss

[jira] [Updated] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

[ https://issues.apache.org/jira/browse/YARN-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-4062: - Summary: Add the flush and compaction functionality via coprocessors and scanners for flow run table (was:

[jira] [Created] (YARN-4070) Add the flush and compaction functionality via coprocessors and scanners for flow activity table

Vrushali C created YARN-4070: Summary: Add the flush and compaction functionality via coprocessors and scanners for flow activity table Key: YARN-4070 URL: https://issues.apache.org/jira/browse/YARN-4070

[jira] [Resolved] (YARN-4063) Populate the flow activity table

[ https://issues.apache.org/jira/browse/YARN-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C resolved YARN-4063. -- Resolution: Duplicate Release Note: The code for flow activity table creation, population and testi

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707617#comment-14707617 ] Vrushali C commented on YARN-3901: -- For long running apps, an entry needs to be made into

[jira] [Updated] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: YARN-3901-YARN-2928.1.patch Uploading patch v01. This patch contains the code that creates and

[jira] [Commented] (YARN-4053) Change the way metric values are stored in HBase Storage

[ https://issues.apache.org/jira/browse/YARN-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715192#comment-14715192 ] Vrushali C commented on YARN-4053: -- The way I see this, it comes down to a basic question

[jira] [Commented] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715208#comment-14715208 ] Vrushali C commented on YARN-4074: -- My take is that we can make things as generic as possi

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720392#comment-14720392 ] Vrushali C commented on YARN-3901: -- Hi [~gtCarrera9] Thanks for the first review pass! To

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