You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2023/01/11 16:15:00 UTC

[jira] [Updated] (UNOMI-724) Implement ElasticSearch rollover recommandation and system to manage current monthly indices

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

Kevan Jahanshahi updated UNOMI-724:
-----------------------------------
    Description: 
A POC have been done to validate the usage of Rollover ES API that combine a lifecycle policy and aliases to replace the current monthly indices rotation.

The goal behind that is to apply current ElasticSearch recommandation on Index/Shards sizing to reduce costs related to monthly indices not being sized correctly due to unpredictable amount of events/sessions per months.

POC PR: [https://github.com/apache/unomi/pull/567]
h2. What remain to be done in current ticket ?
 * Cleanup the POC
 ** Deprecate dateHint parameter in Persistence service layer
 ** Fix session loading (use query to load session with the sessionID for now we will measure performance in a separate ticket: )

> Implement ElasticSearch rollover recommandation and system to manage current monthly indices
> --------------------------------------------------------------------------------------------
>
>                 Key: UNOMI-724
>                 URL: https://issues.apache.org/jira/browse/UNOMI-724
>             Project: Apache Unomi
>          Issue Type: Improvement
>    Affects Versions: unomi-2.1.0
>            Reporter: Kevan Jahanshahi
>            Priority: Major
>             Fix For: unomi-2.2.0
>
>
> A POC have been done to validate the usage of Rollover ES API that combine a lifecycle policy and aliases to replace the current monthly indices rotation.
> The goal behind that is to apply current ElasticSearch recommandation on Index/Shards sizing to reduce costs related to monthly indices not being sized correctly due to unpredictable amount of events/sessions per months.
> POC PR: [https://github.com/apache/unomi/pull/567]
> h2. What remain to be done in current ticket ?
>  * Cleanup the POC
>  ** Deprecate dateHint parameter in Persistence service layer
>  ** Fix session loading (use query to load session with the sessionID for now we will measure performance in a separate ticket: )



--
This message was sent by Atlassian Jira
(v8.20.10#820010)