. You might have delayed results, but
> can prevent them from being empty results for data that's known to be in
> the index.
>
> Thanks.
> -Michael R.
>
> On Dec 5, 2015, at 07:07, Jaskaran Singh <
> jaskaran.si...@comprotechnologies.com> wrote:
>
> Hello All,
>
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
ow me know if there is an existing Jira issue for
addressing the empty entity response when elasticsearch when it is
overloaded. Or should i add one?
Thanks in advance,
Thanks
Jaskaran
On Tue, Dec 8, 2015 at 6:00 PM, Jaskaran Singh <
jaskaran.si...@comprotechnologies.com> wrote:
> Hi Michael,
>
>
Hi Petteri,
Could you post your usergrid-deployment.properties file. This will help in
figuring out the issue.
Also by any chance have you specified the elasticsearch port to 9200 in
your usergrid property config? Normally it should connect on 9300, unless
you have specified the port in your
rther tomorrow 10/6 and fix in Master. I'll reply
> back after I've verified the problem, and subsequently fixed it.
>
> Thanks.
> -Michael
>
> On Wed, Oct 5, 2016 at 7:24 AM, Jaskaran Singh <jaskaran.singh@
> comprotechnologies.com> wrote:
>
>> Hi Michael,
>>
&
;
> curl -i -X PUT -u : "http://localhost:8080/
> system/database/bootstrap"
>
> After starting tomcat and running the above curl commands, it should set
> up the schema and bootstrap the system.
>
> Thanks.
> -Michael R.
>
>
> On Tue, Oct 4, 2016 at
Hello Usergrid Team,
Our application works with Usergrid 1.0.2, 2.1.0 and 2.2.0 (Master branch
from 2nd September commit SHA: 9fae8037a4b881e9c13a5a1f23f71dc34e950c40).
Now, we tried testing our application with the latest 2.2.0 (Master branch
from 1 October SHA:
Hi Usergrid Team,
We are migrating our application from 1.0.2 to 2.2.0 (Master branch, 2nd
September, SHA: 9fae8037a4b881e9c13a5a1f23f71dc34e950c40). We have observed
a new issue (in 2.2.0, Master branch), while using valid client_id &
client_secret. Below is a sample request and response.
Hello Usergrid team,
We were trying to scale our Usergrid Cassandra cluster - Cassandra Datastax
version 2.2.6 & Usergrid version 2.2.
We were able to successfully add a cassandra node to the cluster i.e. it
was automatically detected/discovered (showed up in OPSCENTER). But we
noted that
There is a JIRA for the issue as well:
https://issues.apache.org/jira/browse/USERGRID-1321
On Tue, Apr 4, 2017 at 2:44 PM, Ganaraj Tejasvi <gteja...@gmail.com> wrote:
> Yes. Same issue even now.
>
> On Tue, Apr 4, 2017 at 2:41 PM, Jaskaran Singh <jaskaran.singh@
> comprote
Hi Ganaraj, we were not able to get this to work. Have you tried with the
latest master ?
On Tue, Apr 4, 2017 at 1:25 PM, Ganaraj Tejasvi wrote:
> Hi,
>
> Was this problem with usergrid resolved. If it was resolved could you let
> me know what was the solution to the
Hello Usergrid Team,
We are suddenly facing "out of memory" exceptions in our Tomcat Severs,
under low load conditions. Please note, our usergrid installations have
been very stable over the last 6 months, and we have "not" seen such issues
before. Our setup configuration is as below:
12 matches
Mail list logo