There's already a ticket:
https://issues.apache.org/jira/browse/USERGRID-1051
Just as FYI when we load tested Usergrid to upwards of 10k TPS, we were
using a search queue of 5000. In fact, we made all of the queues have size
of 5000, including the bulk queue.
On Thu, Dec 10, 2015 at 7:17 AM, Jask
Hi Michael,
I am providing an update on my situation. We have changed our application
logic to minimize the use of queries (ie calls with "ql=.") in usergrid
2.x. This seems to have provided significant benefit and all the problems
reported below, seem to have disappeared.
To some extent this
Hi Michael,
This makes sense. I can confirm that while we have been seeing missing
entity errors on high load; these automatically get resolved themselves as
the load decreases.
Another anomaly that we have noticed is that usergrid responds with a code
"401" and message "Unable to authenticate OA
Here are a couple things to check:
1) Can you query all of these entities out when the system is not under load?
2) Elasticsearch has a search queue for index query requests.
(https://www.elastic.co/guide/en/elasticsearch/reference/1.6/modules-threadpool.html)
When this is full the searches are
Hello All,
We are testing usergrid 2.x (master branch) for our application that was
previously being prototyped on usergrid 1.x. We are noticing some weird
anomalies which are causing errors in our application which otherwise works
fine against usergrid 1.x. Specifically, we are seeing empty respo
