[jira] [Commented] (YARN-5236) FlowRunCoprocessor brings down HBase RegionServer

[ https://issues.apache.org/jira/browse/YARN-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326608#comment-15326608 ] Haibo Chen commented on YARN-5236: -- Thanks very much for pointing that out, [~vrushalic]. I completely

[jira] [Created] (YARN-5236) FlowRunCoprocessor brings down HBase RegionServer

Haibo Chen created YARN-5236: Summary: FlowRunCoprocessor brings down HBase RegionServer Key: YARN-5236 URL: https://issues.apache.org/jira/browse/YARN-5236 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-5236) FlowRunCoprocessor brings down HBase RegionServer

[ https://issues.apache.org/jira/browse/YARN-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5236: - Description: The FlowRunCoprocessor, when loaded in HBase, will bring down the region server with

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159168#comment-15159168 ] Haibo Chen commented on YARN-4701: -- The asf warning is unrelated to the patch > When task logs are not

[jira] [Updated] (YARN-4732) *ProcessTree classes have too many whitespace issues

[ https://issues.apache.org/jira/browse/YARN-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4732: - Assignee: Haibo Chen > *ProcessTree classes have too many whitespace issues >

[jira] [Updated] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4697: - Attachment: yarn4697.004.patch New unit tests added for invalid values. Other comments addressed as well

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.004.patch A unit test added to verify the correct http port is displayed when log

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: (was: yarn4701.003.patch) > When task logs are not available, port 8041 is referenced

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.003.patch Fixed the test failures and check style warnings. The rest are unrelated.

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.003.patch > When task logs are not available, port 8041 is referenced instead of port

[jira] [Created] (YARN-4697) NM aggregation thread pool is not bound by limits

Haibo Chen created YARN-4697: Summary: NM aggregation thread pool is not bound by limits Key: YARN-4697 URL: https://issues.apache.org/jira/browse/YARN-4697 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4697: - Attachment: yarn4697.001.patch > NM aggregation thread pool is not bound by limits >

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15149568#comment-15149568 ] Haibo Chen commented on YARN-4697: -- Default value is 100 as defined in YarnConfiguration > NM aggregation

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15150864#comment-15150864 ] Haibo Chen commented on YARN-4697: -- Hi Naganarasimha G R, Thanks very much for your comments. I have

[jira] [Updated] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4697: - Attachment: yarn4697.002.patch > NM aggregation thread pool is not bound by limits >

[jira] [Created] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

Haibo Chen created YARN-4701: Summary: When task logs are not available, port 8041 is referenced instead of port 8042 Key: YARN-4701 URL: https://issues.apache.org/jira/browse/YARN-4701 Project: Hadoop

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.001.patch > When task logs are not available, port 8041 is referenced instead of port

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Description: Accessing logs for an task attempt in the workflow tool in Hue shows "Logs not available for

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.002.patch Thanks for the comments. Addressed. > When task logs are not available,

[jira] [Updated] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4697: - Attachment: yarn4697.003.patch Thanks very much for you guys' comments. I have updated the patch

[jira] [Commented] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200655#comment-15200655 ] Haibo Chen commented on YARN-4766: -- fixed the liscense + checkstyle issues. The unit test failure is

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: (was: yarn4766.001.patch) > NM should not aggregate logs older than the retention policy >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: (was: yarn4766.001.patch) > NM should not aggregate logs older than the retention policy >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.001.patch > NM should not aggregate logs older than the retention policy >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: (was: yarn4766.001.patch) > NM should not aggregate logs older than the retention policy >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.002.patch Addressed checkstyle issues > NM should not aggregate logs older than the

[jira] [Updated] (YARN-4732) *ProcessTree classes have too many whitespace issues

[ https://issues.apache.org/jira/browse/YARN-4732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4732: - Assignee: Gabor Liptak (was: Haibo Chen) > *ProcessTree classes have too many whitespace issues >

[jira] [Created] (YARN-4838) TestLogAggregationService. testLocalFileDeletionOnDiskFull failed

Haibo Chen created YARN-4838: Summary: TestLogAggregationService. testLocalFileDeletionOnDiskFull failed Key: YARN-4838 URL: https://issues.apache.org/jira/browse/YARN-4838 Project: Hadoop YARN

[jira] [Assigned] (YARN-4838) TestLogAggregationService. testLocalFileDeletionOnDiskFull failed

[ https://issues.apache.org/jira/browse/YARN-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reassigned YARN-4838: Assignee: Haibo Chen > TestLogAggregationService. testLocalFileDeletionOnDiskFull failed >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.003.patch > NM should not aggregate logs older than the retention policy >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Issue Type: Improvement (was: Bug) > NM should not aggregate logs older than the retention policy >

[jira] [Created] (YARN-4766) NM should not aggregate logs older than the retention policy

Haibo Chen created YARN-4766: Summary: NM should not aggregate logs older than the retention policy Key: YARN-4766 URL: https://issues.apache.org/jira/browse/YARN-4766 Project: Hadoop YARN

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.004.patch > NM should not aggregate logs older than the retention policy >

[jira] [Commented] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254624#comment-15254624 ] Haibo Chen commented on YARN-4766: -- @Robert Kanter, thanks very much for your review. I have addressed all

[jira] [Updated] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent

[ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5001: - Attachment: yarn5001.001.patch > Aggregated Logs root directory is created with wrong group if nonexistent

[jira] [Updated] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent

[ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5001: - Summary: Aggregated Logs root directory is created with wrong group if nonexistent (was: Aggregated Logs

[jira] [Created] (YARN-5001) Aggregated Logs root directory is created with wrong owner and group if nonexistent

Haibo Chen created YARN-5001: Summary: Aggregated Logs root directory is created with wrong owner and group if nonexistent Key: YARN-5001 URL: https://issues.apache.org/jira/browse/YARN-5001 Project:

[jira] [Updated] (YARN-5001) Aggregated Logs root directory is created with wrong owner and group if nonexistent

[ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5001: - Description: Usually, the group owner for /tmp/logs, where the aggregated logs go, is "hadoop". Under

[jira] [Commented] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292217#comment-15292217 ] Haibo Chen commented on YARN-4766: -- Thanks Ray for your comment, the name you suggested is much better.

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.005.patch > NM should not aggregate logs older than the retention policy >

[jira] [Commented] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296653#comment-15296653 ] Haibo Chen commented on YARN-4766: -- The checkstyle warnings are against the protobuf-generated file. I'll

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: (was: yarn4766.004.patch) > NM should not aggregate logs older than the retention policy >

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.006.patch Rebase the patch on trunk, addressed some of the checkstyle issues. Many of

[jira] [Updated] (YARN-5041) application master log can not be available when clicking jobhistory's am logs link

[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5041: - Attachment: yarn5041.001.patch The patch is tested locally. IMO, the unit test is too difficult to create

[jira] [Updated] (YARN-5041) application master log can not be available when clicking jobhistory's am logs link

[ https://issues.apache.org/jira/browse/YARN-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5041: - Attachment: yarn5041.002.patch Thanks for letting me know. The test failures were indeed caused by my

[jira] [Commented] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent

[ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272908#comment-15272908 ] Haibo Chen commented on YARN-5001: -- The fix will explicitly set the group of /tmp/logs to the group that

[jira] [Updated] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent

[ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5001: - Description: The directory /tmp/logs, where the aggregated logs go, is supposed to be read by JHS. But if

[jira] [Updated] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent

[ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5001: - Description: The directory /tmp/logs, where the aggregated logs go, is supposed to be read by JHS. But if

[jira] [Updated] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4766: - Attachment: yarn4766.004.patch rebased the patch on the latest trunk, fixed the compilation issue > NM

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251022#comment-15251022 ] Haibo Chen commented on YARN-4697: -- [~vinodkv] Upon NM restart, NM will try to recover all applications

[jira] [Commented] (YARN-4766) NM should not aggregate logs older than the retention policy

[ https://issues.apache.org/jira/browse/YARN-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15276598#comment-15276598 ] Haibo Chen commented on YARN-4766: -- findbug issue is unrelated to my patch > NM should not aggregate logs

[jira] [Commented] (YARN-5373) NPE listing wildcard directory in containerLaunch

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378287#comment-15378287 ] Haibo Chen commented on YARN-5373: -- Created a separate jira to fix this issue for Windows, as I don't have

[jira] [Updated] (YARN-5373) NPE listing wildcard directory in containerLaunch

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Description: YARN-4958 added support for wildcards in file localization. It introduces a NPE at

[jira] [Updated] (YARN-5373) NPE listing wildcard directory in containerLaunch

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Priority: Blocker (was: Critical) > NPE listing wildcard directory in containerLaunch >

[jira] [Created] (YARN-5381) fix NPE listing wildcard directory on Windows

Haibo Chen created YARN-5381: Summary: fix NPE listing wildcard directory on Windows Key: YARN-5381 URL: https://issues.apache.org/jira/browse/YARN-5381 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

Haibo Chen created YARN-5373: Summary: NPE introduced by YARN-4958 (The file localization process should allow...) Key: YARN-5373 URL: https://issues.apache.org/jira/browse/YARN-5373 Project: Hadoop YARN

[jira] [Updated] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Description: YARN-4958 added support for wildcards in file localization. It introduces a NPE at

[jira] [Updated] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Description: YARN-4958 added support for wildcards in file localization. It introduces a NPE at

[jira] [Updated] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Description: YARN-4958 added support for wildcards in file localization. It introduces a NPE at

[jira] [Updated] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Description: YARN-4958 added support for wildcards in file localization. It introduces a NPE at

[jira] [Updated] (YARN-5373) NPE listing wildcard directory in containerLaunch

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Summary: NPE listing wildcard directory in containerLaunch (was: NPE introduced by YARN-4958 (The file

[jira] [Commented] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375988#comment-15375988 ] Haibo Chen commented on YARN-5373: -- As per offline discussion with Daniel, the cause is that in a secure

[jira] [Updated] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Priority: Critical (was: Major) > NPE introduced by YARN-4958 (The file localization process should

[jira] [Updated] (YARN-5373) NPE introduced by YARN-4958 (The file localization process should allow...)

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Description: YARN-4958 added support for wildcards in file localization. It introduces a NPE at

[jira] [Commented] (YARN-5381) fix NPE listing wildcard directory on Windows

[ https://issues.apache.org/jira/browse/YARN-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386865#comment-15386865 ] Haibo Chen commented on YARN-5381: -- Per [~templedf]'s comment in YARN-5373, a windows implementation is no

[jira] [Resolved] (YARN-5381) fix NPE listing wildcard directory on Windows

[ https://issues.apache.org/jira/browse/YARN-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen resolved YARN-5381. -- Resolution: Workaround > fix NPE listing wildcard directory on Windows >

[jira] [Updated] (YARN-5373) NPE listing wildcard directory in containerLaunch

[ https://issues.apache.org/jira/browse/YARN-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5373: - Assignee: Daniel Templeton (was: Haibo Chen) > NPE listing wildcard directory in containerLaunch >

[jira] [Updated] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4985: - Attachment: YARN-4985-YARN-5355.prelim.patch > Refactor the coprocessor code & other definition classes

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858743#comment-15858743 ] Haibo Chen commented on YARN-4985: -- Uploading a patch for preliminary review. The hbase-backend module has

[jira] [Commented] (YARN-1593) support out-of-proc AuxiliaryServices

[ https://issues.apache.org/jira/browse/YARN-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15854528#comment-15854528 ] Haibo Chen commented on YARN-1593: -- [~vvasudev] Want to check to see if you have some time to address some

[jira] [Assigned] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reassigned YARN-4985: Assignee: Haibo Chen (was: Vrushali C) > Refactor the coprocessor code & other definition classes

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838583#comment-15838583 ] Haibo Chen commented on YARN-4985: -- [~sjlee0] Can you elaborate a little more on why the schema creator

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15876620#comment-15876620 ] Haibo Chen commented on YARN-4985: -- Apologies for my delayed response! I did not have answers to your

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878866#comment-15878866 ] Haibo Chen commented on YARN-4985: -- Sorry for missing your question, [~sjlee0]. One one hand, FlowScanner

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879219#comment-15879219 ] Haibo Chen commented on YARN-4985: -- Let's leave it as is then. Should we close this as won't fix? >

[jira] [Commented] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881606#comment-15881606 ] Haibo Chen commented on YARN-6218: -- Thanks for the patch [~miklos.szeg...@cloudera.com]! Took a cursory

[jira] [Commented] (YARN-1728) History server doesn't understand percent encoded paths

[ https://issues.apache.org/jira/browse/YARN-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15881397#comment-15881397 ] Haibo Chen commented on YARN-1728: -- Thanks [~yuanbo] for your update! A few more nits. 1) bq. //

[jira] [Updated] (YARN-1728) History server doesn't understand percent encoded paths

[ https://issues.apache.org/jira/browse/YARN-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-1728: - Target Version/s: 2.7.4, 2.8.1, 2.6.6 > History server doesn't understand percent encoded paths >

[jira] [Commented] (YARN-1728) History server doesn't understand percent encoded paths

[ https://issues.apache.org/jira/browse/YARN-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879322#comment-15879322 ] Haibo Chen commented on YARN-1728: -- Thanks [~yuanbo] for the patch! The patch looks good to me except for

[jira] [Commented] (YARN-6218) TestAMRMClient fails with fair scheduler

[ https://issues.apache.org/jira/browse/YARN-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883194#comment-15883194 ] Haibo Chen commented on YARN-6218: -- Thanks for the update, [~miklos.szeg...@cloudera.com]. One nit, the

[jira] [Commented] (YARN-1728) History server doesn't understand percent encoded paths

[ https://issues.apache.org/jira/browse/YARN-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883115#comment-15883115 ] Haibo Chen commented on YARN-1728: -- Latest patch looks good to me. non-binding +1 > History server

[jira] [Commented] (YARN-6030) Eliminate timelineServiceV2 boolean flag in TimelineClientImpl

[ https://issues.apache.org/jira/browse/YARN-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883759#comment-15883759 ] Haibo Chen commented on YARN-6030: -- This issue seems to be no longer valid after YARN-4675, [~gtCarrera9]?

[jira] [Resolved] (YARN-6030) Eliminate timelineServiceV2 boolean flag in TimelineClientImpl

[ https://issues.apache.org/jira/browse/YARN-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen resolved YARN-6030. -- Resolution: Not A Problem > Eliminate timelineServiceV2 boolean flag in TimelineClientImpl >

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879030#comment-15879030 ] Haibo Chen commented on YARN-4985: -- bq. What is the implication of not doing this refactoring? Is the

[jira] [Updated] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4985: - Attachment: YARN-4985-YARN-5355.poc.patch > Refactor the coprocessor code & other definition classes into

[jira] [Assigned] (YARN-6146) Add Builder methods for TimelineEntityFilters

[ https://issues.apache.org/jira/browse/YARN-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reassigned YARN-6146: Assignee: Haibo Chen > Add Builder methods for TimelineEntityFilters >

[jira] [Commented] (YARN-4985) Refactor the coprocessor code & other definition classes into independent packages

[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859912#comment-15859912 ] Haibo Chen commented on YARN-4985: -- The dependency is not mainly because all tests are in the hbase-server

[jira] [Commented] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829025#comment-15829025 ] Haibo Chen commented on YARN-5928: -- Not sure what is causing all the mvn red flags. Unit test failures are

[jira] [Updated] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5928: - Attachment: YARN-5928-YARN-5355.05.patch A newly rebased patch. > Move ATSv2 HBase backend code into a

[jira] [Comment Edited] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827098#comment-15827098 ] Haibo Chen edited comment on YARN-5928 at 1/18/17 12:06 AM: A newly rebased

[jira] [Commented] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827173#comment-15827173 ] Haibo Chen commented on YARN-5928: -- Yes, I believe so. I have tried the standalone timelineservice-hbase

[jira] [Commented] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828607#comment-15828607 ] Haibo Chen commented on YARN-5928: -- Thanks a lot for your reviews, [~sjlee0]! I do see those hadoop*

[jira] [Updated] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5928: - Attachment: YARN-5928-YARN-5355.06.patch A new patch with comments addressed and a lower similarity >

[jira] [Commented] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15828686#comment-15828686 ] Haibo Chen commented on YARN-5928: -- I will upload a patch for trunk shortly. > Move ATSv2 HBase backend

[jira] [Updated] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5928: - Attachment: YARN-5928.06.patch Uploading a patch for branch trunk. > Move ATSv2 HBase backend code into a

[jira] [Commented] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830265#comment-15830265 ] Haibo Chen commented on YARN-5928: -- As before, the unit tests are not related. > Move ATSv2 HBase backend

[jira] [Updated] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-5928: - Attachment: YARN-5928-YARN-5355.07.patch Uploading a new patch for branch YARN-5355 to resolve the

[jira] [Resolved] (YARN-5667) Move HBase backend code in ATS v2 into its separate module

[ https://issues.apache.org/jira/browse/YARN-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen resolved YARN-5667. -- Resolution: Done > Move HBase backend code in ATS v2 into its separate module >

[jira] [Commented] (YARN-5928) Move ATSv2 HBase backend code into a new module that is only dependent at runtime by yarn servers

[ https://issues.apache.org/jira/browse/YARN-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832181#comment-15832181 ] Haibo Chen commented on YARN-5928: -- Thanks [~sjlee0] for your reviews! > Move ATSv2 HBase backend code

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

[ https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888479#comment-15888479 ] Haibo Chen commented on YARN-4821: -- [~Naganarasimha], have you got cycles to continue on this jira? >

  1   2   3   4   5   6   7   8   9   10   >