You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@unomi.apache.org by "David Griffon (Jira)" <ji...@apache.org> on 2022/06/06 17:56:00 UTC

[jira] [Closed] (UNOMI-567) Unomi logs heavily polluted

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

David Griffon closed UNOMI-567.
-------------------------------
    Resolution: Fixed

A custom log level is now set on ES Client to avoid this log pollution

> Unomi logs heavily polluted
> ---------------------------
>
>                 Key: UNOMI-567
>                 URL: https://issues.apache.org/jira/browse/UNOMI-567
>             Project: Apache Unomi
>          Issue Type: New Feature
>    Affects Versions: 2.0.0, 1.6.0
>            Reporter: David Griffon
>            Assignee: David Griffon
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> When running unomi with ES > 7.16, there are way too many logs, due to this error: 
> {code:java}
> May  2 08:17:16 ip-10-0-3-182 docker_jcustomer[9846]: 08:17:16.236 [pool-18-thread-1] WARN  org.elasticsearch.client.RestClient -  request [POST http://elasticsearch:9200/context-rule/_search?typed_keys=true&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&scroll=1h&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true] returned 1 warnings: [299 Elasticsearch-7.17.1-e5acb99f822233d62d6444ce45a4543dc1c8059a "[ignore_throttled] parameter is deprecated because frozen indices have been deprecated. Consider cold or frozen tiers in place of frozen indices."] 
> {code}
> This happens because of a warning generated by ES because of the {{ignore_throttled}} that has been deprecated.
> We use the High Level client (provided by ES) to communnicate with ES, it  includes ignore_throttled as parameter, we cannot move to the latest version because license issue (after 7.10.2 license is no more apache2)
> In order to fix it, we now change the log level of the RestClient to not display warnings.
> If one wants to have them back the configuration {{errorLogLevelRestClient}} restores the original behavior



--
This message was sent by Atlassian Jira
(v8.20.7#820007)