[
https://issues.apache.org/jira/browse/FALCON-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286986#comment-14286986
]
Pallavi Rao commented on FALCON-1004:
-------------------------------------
it is most likely that the configuration store initialization takes the
longest. The reason for that is that all the configuration files stored on HFDS
files are read and an in memory data structure is populated. With increased
number of entities, it is bound to take longer to read files serially. Two
possible ways to solve it:
1. Short term - Read the files and load the config in parallel, rather than
sequentially.
2. Long term - Choose a config store that is better optimized for
lookups/updates.
> Prism server takes longer to start with increased number of entities
> --------------------------------------------------------------------
>
> Key: FALCON-1004
> URL: https://issues.apache.org/jira/browse/FALCON-1004
> Project: Falcon
> Issue Type: Bug
> Reporter: Pallavi Rao
> Assignee: Pallavi Rao
>
> What was reported by InMobi Ops team - "With increase in feeds and process,
> the prism start time is taking long.
> We need to improve on prism start time, as with cluster update, or prism
> bounce the wait time it increasing, before we start using the services. we
> have 2K+ Feeds, and 400+ Process as of now, and prism takes around 25mins to
> start the service."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
