[ 
https://issues.apache.org/jira/browse/USERGRID-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615463#comment-14615463
 ] 

David Johnson commented on USERGRID-778:
----------------------------------------

Having a hard time reproducing this problem in production, e.g. 20 queries in a 
a row an none failed:

$ ./curl.sh
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750
    750    2250   39750

> Limit on Queries results in a highly variable number of results
> ---------------------------------------------------------------
>
>                 Key: USERGRID-778
>                 URL: https://issues.apache.org/jira/browse/USERGRID-778
>             Project: Usergrid
>          Issue Type: Bug
>            Reporter: Jeffrey 
>            Assignee: David Johnson
>
> This behavior is observed on a build from the two-dot-o branch with commit ID 
> 2d1c8b8ac7b20b63a11d83adca56839d8b409cca.
> For example, limit=2 gives you 1 sometimes, limit=750 gives anywhere from 625 
> to 749.  For example this script:
> {code}
> #!/bin/bash
> for count in 1 2 3 4 5 6 7 8 9 10
> do 
>     curl -s 
> "https://example.com/appservices/testorg/sandbox/scmocks?limit=750"; > 
> file${count}
>     grep uuid file${count} | wc
>     rm file${count}
> done
> {code}
> Produces these results:
>      685    2055   36305
>      750    2250   39750
>      749    2247   39697
>      742    2226   39326
>      750    2250   39750
>      749    2247   39697
>      747    2241   39591
>      744    2232   39432
>      750    2250   39750
>      749    2247   39697
> A different count every time.



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

Reply via email to