You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@unomi.apache.org by "Francois Gerthoffert (Jira)" <ji...@apache.org> on 2023/03/21 13:47:00 UTC

[jira] [Updated] (UNOMI-465) Unomi stops saving events when elastic enters readOnly mode. No way to see that something is wrong on client side.

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

Francois Gerthoffert updated UNOMI-465:
---------------------------------------
    Fix Version/s: unomi-2.3.0
                       (was: unomi-2.2.0)

> Unomi stops saving events when elastic enters readOnly mode. No way to see that something is wrong on client side.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: UNOMI-465
>                 URL: https://issues.apache.org/jira/browse/UNOMI-465
>             Project: Apache Unomi
>          Issue Type: Bug
>          Components: unomi(-core)
>    Affects Versions: unomi-1.5.4
>            Reporter: Risto Kowaczewski
>            Priority: Critical
>             Fix For: unomi-2.3.0
>
>
> I encountered the following error. When elasticsearch server has very little disk space it can go into read-only mode. Then it stops saving data. But there is no way the client (GUI, etc) knows that there is a problem.
> If you do not monitor elastic then you can go days without data being saved.  I guess I will have to monitor elastic from GUI to alert users that something is not ok. 
> This happens also when you create rule, segment, etc.
> Suggested approach is to use HTTP protocol as it is. And return data as it is but insted of 200 code return: 422 Unprocessable Entity.
> 422 Unprocessable Entity response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions. 
> Using this approach will ensure that context server and the rest of unomi works but it indicates that there is something wrong. 



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