You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Jon Zeolla (JIRA)" <ji...@apache.org> on 2017/05/01 16:18:04 UTC

[jira] [Issue Comment Deleted] (METRON-518) Add performance tuning settings to Elasticsearch

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

Jon Zeolla updated METRON-518:
------------------------------
    Comment: was deleted

(was: We should also consider better tokenizers for some fields such as https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-pathhierarchy-tokenizer.html#analysis-pathhierarchy-tokenizer)

> Add performance tuning settings to Elasticsearch
> ------------------------------------------------
>
>                 Key: METRON-518
>                 URL: https://issues.apache.org/jira/browse/METRON-518
>             Project: Metron
>          Issue Type: Sub-task
>            Reporter: Jon Zeolla
>              Labels: performance
>
> Elasticsearch has a lot of knobs that can be turned in order to speed up the efficiency of your cluster.  A lot of those depend on your specific use case, and in this case we have a well defined use case and format of documents.  We should do a better job of adding those by default.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)