[
https://issues.apache.org/jira/browse/AMBARI-17505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361143#comment-15361143
]
Hadoop QA commented on AMBARI-17505:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816007/AMBARI-17505.2.2-next.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7672//console
This message is automatically generated.
> Optimize class path scanning
> -----------------------------
>
> Key: AMBARI-17505
> URL: https://issues.apache.org/jira/browse/AMBARI-17505
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Laszlo Puskas
> Assignee: Laszlo Puskas
> Fix For: 2.5.0
>
> Attachments: AMBARI-17505.2.2-next.patch, AMBARI-17505.v2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Problem:
> When looking up upgrade checks the whole ambari server package is scanned
> that considerably increases the server start time.
> Solution:
> Scan only the specific package that contains upgradecheck implementations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
