ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20262) Startup Annotation Scanning Takes Too Long
Date Wed, 01 Mar 2017 20:52:45 GMT

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

Jonathan Hurley updated AMBARI-20262:
-------------------------------------
    Attachment: AMBARI-20262.patch

> Startup Annotation Scanning Takes Too Long
> ------------------------------------------
>
>                 Key: AMBARI-20262
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20262
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20262.patch
>
>
> Currently, Ambari uses Spring's {{ClassPathScanningCandidateComponentProvider}} along
with an {{AnnotationTypeFilter}} to find classes annotated in our classpath:
> {code}
>       ClassPathScanningCandidateComponentProvider scanner =
>           new ClassPathScanningCandidateComponentProvider(false);
>       // match only singletons that are eager listeners
>       for (Class<? extends Annotation> cls : classes) {
>         scanner.addIncludeFilter(new AnnotationTypeFilter(cls));
>       }
>       beanDefinitions = scanner.findCandidateComponents(AMBARI_PACKAGE);
> {code}
> This takes roughly 19 seconds on normal deployments. We can reduce this time to roughly
8 seconds by switching over to Google's {{ClassPath}} via our internal {{ClasspathScannerUtils}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message