[
https://issues.apache.org/jira/browse/METRON-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449941#comment-16449941
]
Simon Elliston Ball commented on METRON-1538:
---------------------------------------------
Absolutely. In general I agree with your thoughts, just not sure we want to
make the user make the choice and add to our already complex grid of
co-dependent tuning variables.
> Don't use GUIDS for Elastic document id, but autogenerated ID's for
> performance
> -------------------------------------------------------------------------------
>
> Key: METRON-1538
> URL: https://issues.apache.org/jira/browse/METRON-1538
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.4.3
> Reporter: Ward Bekker
> Priority: Major
> Labels: performance
>
> Metron currently uses GUIDS for ES document Ids, this goes against the best
> practice:
> "When indexing a document that has an explicit id, Elasticsearch needs to
> check whether a document with the same id already exists within the same
> shard, which is a costly operation and gets even more costly as the index
> grows. By using auto-generated ids, Elasticsearch can skip this check, which
> makes indexing faster."
> [https://www.elastic.co/guide/en/elasticsearch/reference/master/tune-for-indexing-]speed.html#_use_auto_generated_ids
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
