ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laszlo Puskas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17505) Optimize class path scanning
Date Fri, 01 Jul 2016 09:33:11 GMT

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

Laszlo Puskas updated AMBARI-17505:
-----------------------------------
    Status: Open  (was: Patch Available)

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

Mime
View raw message