You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Laszlo Puskas (JIRA)" <ji...@apache.org> on 2016/06/30 16:08:10 UTC

[jira] [Updated] (AMBARI-17505) Optimize class path scanning

     [ https://issues.apache.org/jira/browse/AMBARI-17505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Laszlo Puskas updated AMBARI-17505:
-----------------------------------
    Attachment: AMBARI-17505.v1.patch

> 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.v1.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)