[
https://issues.apache.org/jira/browse/USERGRID-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey resolved USERGRID-407.
-------------------------------
Resolution: Won't Fix
no longer relevant with 2.1 refactoring
> Index allocation incorrectly re-allocates the default index
> -----------------------------------------------------------
>
> Key: USERGRID-407
> URL: https://issues.apache.org/jira/browse/USERGRID-407
> Project: Usergrid
> Issue Type: Bug
> Reporter: Todd Nine
> Assignee: Todd Nine
> Priority: Critical
>
> After we allocate a new index and the write alias moves to it, we have 2 or
> more actual elasticsearch indexes. If I delete the original index, which is
> now a read only index. The application will incorrectly re-allocate this
> index the next time the application is started.
> Instead, if the write alias exists, no index should be automatically
> allocated unless explicitly instructed to do so by the user.
> This way new indexes can be created, data can be migrated into these indexes,
> and old indexes deleted to reclaim space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
