[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568128#comment-14568128 ] Li Lu commented on YARN-3051: - Hi [~varun_saxena], thanks for the work! Not sure if you've alre

[jira] [Commented] (YARN-3699) Decide if flow version should be part of row key or column

[ https://issues.apache.org/jira/browse/YARN-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567756#comment-14567756 ] Li Lu commented on YARN-3699: - I'm +1 on removing the flow version section from the row key. I

[jira] [Commented] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563415#comment-14563415 ] Li Lu commented on YARN-3721: - Since YARN-3726 is in, maybe we can commit this one soon? [~zjsh

[jira] [Commented] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562080#comment-14562080 ] Li Lu commented on YARN-3721: - Yes, I agree. We do have the required module because we directly

[jira] [Updated] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3721: Attachment: YARN-3721-YARN-2928.002.patch We are indeed depending on hbase-test-util since we need to launch mini hba

[jira] [Updated] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3721: Attachment: YARN-3721-YARN-2928.002.patch We are indeed depending on hbase-test-util since we need to launch mini hba

[jira] [Commented] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560415#comment-14560415 ] Li Lu commented on YARN-3721: - Also, [~sjlee0], I thought I've resolved the problem, but would

[jira] [Commented] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560406#comment-14560406 ] Li Lu commented on YARN-3721: - Hi [~sjlee0], I'm not 100% sure, but at least on my local machin

[jira] [Commented] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560352#comment-14560352 ] Li Lu commented on YARN-3721: - Seems like the HBase UT is also failing on YARN-2928 branch. [~v

[jira] [Updated] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3721: Attachment: YARN-3721-YARN-2928.001.patch Add an exclusion to resolve the cyclic dependency in timelineserver's pom f

[jira] [Commented] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560247#comment-14560247 ] Li Lu commented on YARN-3721: - Hi [~sjlee0], thanks for catching this! Wow, this is a real prob

[jira] [Assigned] (YARN-3721) build is broken on YARN-2928 branch due to possible dependency cycle

[ https://issues.apache.org/jira/browse/YARN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu reassigned YARN-3721: --- Assignee: Li Lu > build is broken on YARN-2928 branch due to possible dependency cycle > -

[jira] [Updated] (YARN-3702) Timeline service v2 load generator needs to write event id

[ https://issues.apache.org/jira/browse/YARN-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3702: Attachment: YARN-3702-YARN-2928.001.patch trivial patch to add a sample timeline event id for the SimpleEntityWriter.

[jira] [Created] (YARN-3702) Timeline service v2 load generator needs to write event id

Li Lu created YARN-3702: --- Summary: Timeline service v2 load generator needs to write event id Key: YARN-3702 URL: https://issues.apache.org/jira/browse/YARN-3702 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554690#comment-14554690 ] Li Lu commented on YARN-3411: - Sorry about the delayed reply. Firstly, I thought flowVersion wa

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553369#comment-14553369 ] Li Lu commented on YARN-3411: - I looked at the latest patch and think it's in a good shape for

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553186#comment-14553186 ] Li Lu commented on YARN-3411: - Hi [~vrushalic], sure, don't worry about the test code clean up

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551265#comment-14551265 ] Li Lu commented on YARN-3051: - Hi [~varun_saxena], I just tried to apply the patch against the

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14551238#comment-14551238 ] Li Lu commented on YARN-3411: - Hi [~vrushalic], thanks for working on this! I just got back and

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547304#comment-14547304 ] Li Lu commented on YARN-3051: - Hi [~varun_saxena], I think the new patch name pattern should be

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545857#comment-14545857 ] Li Lu commented on YARN-3411: - Hi [~djp]! I totally agree with your concerns. However, for now

[jira] [Commented] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540935#comment-14540935 ] Li Lu commented on YARN-3529: - Great! Thanks for the update! > Add miniHBase cluster and Phoe

[jira] [Commented] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540844#comment-14540844 ] Li Lu commented on YARN-3529: - Thanks [~zjshen] for the review and commit! [~vrushalic] if you

[jira] [Updated] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3529: Attachment: YARN-3529-YARN-2928.003.patch Thanks [~zjshen]! I forgot to move this part. Nice catch! > Add miniHBase

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540211#comment-14540211 ] Li Lu commented on YARN-3411: - Hi [~vrushalic], sorry to hear the trouble. Have you tried to ap

[jira] [Updated] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3529: Attachment: YARN-3529-YARN-2928.002.patch New patch to fix the findbugs warnings. > Add miniHBase cluster and Phoen

[jira] [Updated] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3529: Attachment: YARN-3529-YARN-2928.001.patch New patch addressed [~zjshen]'s comments. I changed maven organization for

[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 ] Li Lu updated YARN-3545: Attachment: YARN-3545-YARN-2928.000.patch In this patch I'm using concurrent hash map to replace synchronized hash ma

[jira] [Commented] (YARN-3595) Performance optimization using connection cache of Phoenix timeline writer

[ https://issues.apache.org/jira/browse/YARN-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538341#comment-14538341 ] Li Lu commented on YARN-3595: - Hi [~sjlee0], thanks for the suggestions. I think you're right t

[jira] [Updated] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3529: Attachment: YARN-3529-YARN-2928.000.patch Attach a patch to add miniHbasecluster and Phoenix support in our unit test

[jira] [Commented] (YARN-3595) Performance optimization using connection cache of Phoenix timeline writer

[ https://issues.apache.org/jira/browse/YARN-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535945#comment-14535945 ] Li Lu commented on YARN-3595: - I put some thoughts on this. The problem of simply letting the w

[jira] [Commented] (YARN-3426) Add jdiff support to YARN

[ https://issues.apache.org/jira/browse/YARN-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535903#comment-14535903 ] Li Lu commented on YARN-3426: - Sure. I'll cancel the patch. > Add jdiff support to YARN > ---

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535676#comment-14535676 ] Li Lu commented on YARN-3134: - I've updated the patch according to latest comments. I addressed

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.007.patch > [Storage implementation] Exploiting the option of using Phoenix to access

[jira] [Updated] (YARN-3595) Performance optimization using connection cache of Phoenix timeline writer

[ https://issues.apache.org/jira/browse/YARN-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3595: Description: The story about the connection cache in Phoenix timeline storage is a little bit long. In YARN-3033 we

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533890#comment-14533890 ] Li Lu commented on YARN-644: Thanks [~varun_saxena]! The latest patch LGTM. I'd appreciate verif

[jira] [Updated] (YARN-3595) Performance optimization using connection cache of Phoenix timeline writer

[ https://issues.apache.org/jira/browse/YARN-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3595: Summary: Performance optimization using connection cache of Phoenix timeline writer (was: Performance optimization f

[jira] [Updated] (YARN-3595) Performance optimization using connection cache of Phoenix timeline writer

[ https://issues.apache.org/jira/browse/YARN-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3595: Description: The story about the connection cache in Phoenix timeline storage is a little bit long. In YARN-3033 we

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533883#comment-14533883 ] Li Lu commented on YARN-3134: - Looked into the concurrency bug. The problem is caused by concur

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533880#comment-14533880 ] Li Lu commented on YARN-644: Oh I mean the access modifiers. Can we use default level since all

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533866#comment-14533866 ] Li Lu commented on YARN-644: Hi [~varun_saxena], thanks for working on this! The patch is mostly

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533671#comment-14533671 ] Li Lu commented on YARN-3134: - Looking into this. Seems like we need more fine tunes for the sy

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533670#comment-14533670 ] Li Lu commented on YARN-3134: - Sure, I'll make those clean up changes. > [Storage implementat

[jira] [Updated] (YARN-1427) yarn-env.cmd should have the analog comments that are in yarn-env.sh

[ https://issues.apache.org/jira/browse/YARN-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-1427: Attachment: YARN-1427-trunk.2.patch I'm not sure why the previous patch did not apply to our latest trunk. I'm regen

[jira] [Commented] (YARN-1329) yarn-config.sh overwrites YARN_CONF_DIR indiscriminately

[ https://issues.apache.org/jira/browse/YARN-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533468#comment-14533468 ] Li Lu commented on YARN-1329: - Quick note: this patch no longer applies to trunk. The current y

[jira] [Commented] (YARN-1832) wrong MockLocalizerStatus.equals() method implementation

[ https://issues.apache.org/jira/browse/YARN-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533457#comment-14533457 ] Li Lu commented on YARN-1832: - This patch still applies to the latest trunk (as of now). LGTM.

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533448#comment-14533448 ] Li Lu commented on YARN-644: Hi [~varun_saxena], thanks for the patch! Asserting on the content

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.006.patch > [Storage implementation] Exploiting the option of using Phoenix to access

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: (was: YARN-3134-YARN-2928.006.patch) > [Storage implementation] Exploiting the option of using Phoeni

[jira] [Commented] (YARN-3276) Refactor and fix null casting in some map cast for TimelineEntity (old and new)

[ https://issues.apache.org/jira/browse/YARN-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533412#comment-14533412 ] Li Lu commented on YARN-3276: - Patch LGTM. +1 pending Jenkins. BTW, I have successfully appli

[jira] [Updated] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3411: Labels: (was: BB2015-05-TBR) > [Storage implementation] explore the native HBase write schema for storage > ---

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Labels: (was: BB2015-05-TBR) > [Storage implementation] Exploiting the option of using Phoenix to access > HBase b

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533393#comment-14533393 ] Li Lu commented on YARN-3134: - I just opened YARN-3595 to trace all connection cache related di

[jira] [Created] (YARN-3595) Performance optimization for the connection cache of Phoenix timeline writer

Li Lu created YARN-3595: --- Summary: Performance optimization for the connection cache of Phoenix timeline writer Key: YARN-3595 URL: https://issues.apache.org/jira/browse/YARN-3595 Project: Hadoop YARN

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.006.patch Thanks [~zjshen] and [~djp] for the review! In this patch I removed the un

[jira] [Updated] (YARN-20) More information for "yarn.resourcemanager.webapp.address" in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-20: -- Assignee: Bartosz Ługowski > More information for "yarn.resourcemanager.webapp.address" in yarn-default.xml > -

[jira] [Commented] (YARN-20) More information for "yarn.resourcemanager.webapp.address" in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533010#comment-14533010 ] Li Lu commented on YARN-20: --- The latest patch (v2) LGTM. > More information for "yarn.resourceman

[jira] [Commented] (YARN-3513) Remove unused variables in ContainersMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531946#comment-14531946 ] Li Lu commented on YARN-3513: - bq. my intention was to actually capture the total usage when th

[jira] [Commented] (YARN-3562) unit tests failures and issues found from findbug from earlier ATS checkins

[ https://issues.apache.org/jira/browse/YARN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531919#comment-14531919 ] Li Lu commented on YARN-3562: - Patch LGTM. Thanks for fixing this [~Naganarasimha]! > unit te

[jira] [Commented] (YARN-3513) Remove unused variables in ContainersMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531917#comment-14531917 ] Li Lu commented on YARN-3513: - Hi [~Naganarasimha], thanks for working on this. After looking a

[jira] [Commented] (YARN-868) YarnClient should set the service address in tokens returned by getRMDelegationToken()

[ https://issues.apache.org/jira/browse/YARN-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531776#comment-14531776 ] Li Lu commented on YARN-868: Hi [~varun_saxena], thanks for working on this! I agree with [~djp]

[jira] [Commented] (YARN-679) add an entry point that can start any Yarn service

[ https://issues.apache.org/jira/browse/YARN-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531743#comment-14531743 ] Li Lu commented on YARN-679: Hi [~ste...@apache.org], thanks for working on this. I have one que

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531731#comment-14531731 ] Li Lu commented on YARN-644: Hi [~varun_saxena], sorry I accidentally assigned this JIRA to myse

[jira] [Updated] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-644: --- Assignee: Varun Saxena (was: Li Lu) > Basic null check is not performed on passed in arguments before using them in >

[jira] [Assigned] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu reassigned YARN-644: -- Assignee: Li Lu (was: Varun Saxena) > Basic null check is not performed on passed in arguments before using them

[jira] [Updated] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-644: --- Labels: BB2015-05-TBR newbie (was: BB2015-05-TBR) > Basic null check is not performed on passed in arguments before usi

[jira] [Commented] (YARN-81) Make sure YARN declares correct set of dependencies

[ https://issues.apache.org/jira/browse/YARN-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531551#comment-14531551 ] Li Lu commented on YARN-81: --- Hi [~djp], thanks for working on this! On my local machine I found sim

[jira] [Updated] (YARN-20) More information for "yarn.resourcemanager.webapp.address" in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-20: -- Labels: BB2015-05-TBR newbie (was: BB2015-05-TBR) > More information for "yarn.resourcemanager.webapp.address" in yarn-def

[jira] [Commented] (YARN-20) More information for "yarn.resourcemanager.webapp.address" in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531512#comment-14531512 ] Li Lu commented on YARN-20: --- Hi [~noddi], thanks for working on this! I'm wondering why {{yarn.http

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.005.patch Thanks [~djp] and [~zjshen] for the review! I updated the patch according t

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531329#comment-14531329 ] Li Lu commented on YARN-3554: - I think the current conclusion on HADOOP-11398 is that we need t

[jira] [Commented] (YARN-3529) Add miniHBase cluster and Phoenix support to ATS v2 unit tests

[ https://issues.apache.org/jira/browse/YARN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529689#comment-14529689 ] Li Lu commented on YARN-3529: - Thanks for the help from [~swagle] and [~vrushalic]! Now I have

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.004.patch I've addressed all comments from [~zjshen] except for two points: I think w

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529377#comment-14529377 ] Li Lu commented on YARN-3134: - Thanks [~zjshen]! I'm addressing your comments. Meanwhile, I thi

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527632#comment-14527632 ] Li Lu commented on YARN-3134: - And, one more thing: I'm closing all PreparedStatements implicit

[jira] [Updated] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3134: Attachment: YARN-3134-YARN-2928.003.patch Updated my patch according to the latest comments. I've rebased the patch t

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527442#comment-14527442 ] Li Lu commented on YARN-3551: - The latest patch LGTM. +1 for commit. > Consolidate data model

[jira] [Commented] (YARN-3513) Remove unused variables in ContainersMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525412#comment-14525412 ] Li Lu commented on YARN-3513: - No I was talking about these lines in YARN-3334: {code} +

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525406#comment-14525406 ] Li Lu commented on YARN-3554: - Hi [~Naganarasimha], I just wanted to bring that JIRA into atten

[jira] [Resolved] (YARN-3407) HttpServer2 Max threads in TimelineCollectorManager should be more than 10

[ https://issues.apache.org/jira/browse/YARN-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu resolved YARN-3407. - Resolution: Later I'm closing this as "Later" in case we need to do performance tuning after we reached that phase

[jira] [Commented] (YARN-3407) HttpServer2 Max threads in TimelineCollectorManager should be more than 10

[ https://issues.apache.org/jira/browse/YARN-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524337#comment-14524337 ] Li Lu commented on YARN-3407: - Performance tuning for timeline v2 is a comprehensive problem. I

[jira] [Updated] (YARN-3407) HttpServer2 Max threads in TimelineCollectorManager should be more than 10

[ https://issues.apache.org/jira/browse/YARN-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3407: Issue Type: Sub-task (was: Bug) Parent: YARN-2928 > HttpServer2 Max threads in TimelineCollectorManager shou

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14524328#comment-14524328 ] Li Lu commented on YARN-3401: - I just changed the title of this JIRA to security so that we're

[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 ] Li Lu updated YARN-3401: Summary: [Security] users should not be able to create a generic TimelineEntity and associate arbitrary type (was: [

[jira] [Updated] (YARN-3422) relatedentities always return empty list when primary filter is set

[ https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3422: Labels: newbie (was: ) > relatedentities always return empty list when primary filter is set > -

[jira] [Updated] (YARN-3460) Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM

[ https://issues.apache.org/jira/browse/YARN-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3460: Component/s: (was: test) > Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM > ---

[jira] [Updated] (YARN-3460) Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM

[ https://issues.apache.org/jira/browse/YARN-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3460: Component/s: test > Test TestSecureRMRegistryOperations failed with IBM_JAVA JVM > --

[jira] [Commented] (YARN-3477) TimelineClientImpl swallows exceptions

[ https://issues.apache.org/jira/browse/YARN-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524295#comment-14524295 ] Li Lu commented on YARN-3477: - Hi [~ste...@apache.org], thanks for the patch! The fixes on the

[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&focusedCommentId=14524247#comment-14524247 ] Li Lu commented on YARN-3509: - Hi [~zjshen], thanks for working on this. I'm wondering if this

[jira] [Commented] (YARN-3380) Add protobuf compatibility checker to jenkins test runs

[ https://issues.apache.org/jira/browse/YARN-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524232#comment-14524232 ] Li Lu commented on YARN-3380: - Hi [~sidharta-s], thanks for poking. Right now my bandwidth is l

[jira] [Updated] (YARN-3484) Fix up yarn top shell code

[ https://issues.apache.org/jira/browse/YARN-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3484: Labels: newbie (was: ) > Fix up yarn top shell code > -- > > Key: YARN-3484

[jira] [Commented] (YARN-3513) Remove unused variables in ContainersMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524215#comment-14524215 ] Li Lu commented on YARN-3513: - Hi [~Naganarasimha], thanks for the patch. +1 for removing {{vme

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524197#comment-14524197 ] Li Lu commented on YARN-3554: - This is just a quick note that there's another JIRA YARN-3518 th

[jira] [Updated] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time

[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3518: Labels: newbie (was: ) > default rm/am expire interval should not less than default resourcemanager > connect wait

[jira] [Updated] (YARN-3518) default rm/am expire interval should not less than default resourcemanager connect wait time

[ https://issues.apache.org/jira/browse/YARN-3518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3518: Labels: configuration newbie (was: newbie) > default rm/am expire interval should not less than default resourcemana

[jira] [Updated] (YARN-3513) Remove unused variables in ContainersMonitorImpl

[ https://issues.apache.org/jira/browse/YARN-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3513: Labels: newbie (was: ) > Remove unused variables in ContainersMonitorImpl >

[jira] [Commented] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

[ https://issues.apache.org/jira/browse/YARN-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524179#comment-14524179 ] Li Lu commented on YARN-3523: - Thanks [~Naganarasimha]! The quick fix LGTM. > Cleanup Resource

[jira] [Updated] (YARN-3523) Cleanup ResourceManagerAdministrationProtocol interface audience

[ https://issues.apache.org/jira/browse/YARN-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3523: Labels: newbie (was: ) > Cleanup ResourceManagerAdministrationProtocol interface audience >

[jira] [Updated] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3528: Labels: test (was: ) > Tests with 12345 as hard-coded port break jenkins > -

[jira] [Updated] (YARN-3552) RM Web UI shows -1 running containers for completed apps

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3552: Labels: newbie (was: ) > RM Web UI shows -1 running containers for completed apps >

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