[
https://issues.apache.org/jira/browse/USERGRID-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey updated USERGRID-469:
------------------------------
Summary: [FIXED?] Investigate using a new TimeUUID as our routing value
(was: Investigate using a new TimeUUID as our routing value)
> [FIXED?] Investigate using a new TimeUUID as our routing value
> --------------------------------------------------------------
>
> Key: USERGRID-469
> URL: https://issues.apache.org/jira/browse/USERGRID-469
> Project: Usergrid
> Issue Type: Story
> Reporter: Todd Nine
> Fix For: 2.1.0
>
>
> We have been using our entityId as our routing value. This gives us a much
> better distribution than our documentId format. However, when a node will be
> heavily connected, it will introduce a hotspot in our ES cluster. Instead,
> we should either route based a new time UUID a new time uuid just for
> routing. This way we can put each de-normalized document on it's own shard,
> regardless of collection membership or connections.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
