[
https://issues.apache.org/jira/browse/AMBARI-17505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361155#comment-15361155
]
Hudson commented on AMBARI-17505:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #5219 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5219/])
AMBARI-17505. Optimize class path scanning. (Laszlo Puskas via stoader)
(stoader:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d6abf7377b2c95bf8502e953c4935a3edc55b5a3])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
> 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)
