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

Posted to dev@usergrid.apache.org by "Jeffrey (JIRA)" <ji...@apache.org> on 2015/07/12 23:34:04 UTC

[jira] [Closed] (USERGRID-565) Evaluate Node Client for next release

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

Jeffrey  closed USERGRID-565.
-----------------------------

We have implemented the node client

> Evaluate Node Client for next release
> -------------------------------------
>
>                 Key: USERGRID-565
>                 URL: https://issues.apache.org/jira/browse/USERGRID-565
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Jeffrey 
>            Assignee: Todd Nine
>            Priority: Critical
>             Fix For: 2.1
>
>
> I regularly see a large queue in ElasticSearch on a single node and the messages are not getting distributed across the cluster.  The backlog in the single node can be cleared by increasing thread pool size, allowing jobs to get sent to the other nodes.
> the node client will help direct jobs to the correct ES node and not develop a backlog.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)