We used HTTP API to reproduce the problem.  It is related database return
less records in certain time. But it may caused by xxxMs time different
between two machines.   influxdb could not return the records beyond
now().  Is there a suggestion for how to solve this kind of problem?

Lee

On Tue, Jun 28, 2016 at 2:17 AM, Sean Beckett <[email protected]> wrote:

> Can you recreate the issue using the CLI or the HTTP API directly, just to
> ensure there's not something happening in the javascript layer?
>
> On Sun, Jun 26, 2016 at 7:09 PM, yueyue papa <[email protected]> wrote:
>
>> good to get these information.  I will redo on 0.13 version.
>>
>> Current status:
>>
>> >> What's in the logs during the queries? Any write errors?
>> No write error. The data is in the influxdb.   The data will be query out
>> after 1~2 s.
>>
>> >> What version of InfluxDB?
>> I am using 0.12.  I read the changed information.
>>
>> >> How are you writing points? HTTP API? UDP? Graphite? Telegraf?
>> HTTP APIs.  Using client v1
>>
>> >> Can you provide some sample output from the queries, showing the
>> points "appearing" later?
>>
>> SELECT xxxx FROM eventlog WHERE time >= '2016-06-23T08:42:06.343Z' AND
>> machine='xxx' order by time limit 1000
>>
>> HTTP client: select result
>> angular.js:12783 queryEvents eventTime:2016-06-23T16:42:26.312Z
>> angular.js:12783 Thu Jun 23 2016 16:42:26 GMT+0800 (CST)
>> angular.js:12783
>> http://localhost:3003/am/icmcc/1/query/1/ev/1000/2016-06-23T08:42:26.312Z
>> angular.js:12783 parseEvents:1:2016-06-23T16:42:26.022Z,PICK/DROP
>> TIME:125, XCH:/cluster:$1/chmbXfer:$1, arm:0, CH:/cluster:$1/chmbCVD:$CHC,
>> "Rcp1_Glass461", "Src - lift_glass/robot_pick_glass",R,,,TC,,1074069510,,,1
>> angular.js:12783 parseEvents:1:2016-06-23T16:42:26.023Z,RETRACT TIME:125,
>> XCH:/cluster:$1/chmbXfer:$1, arm:0, CH:/cluster:$1/chmbCVD:$CHC,
>> "Rcp1_Glass461", "Src - retract_glass",R,,,TC,,1074069511,,,1
>> angular.js:12783 parseEvents:1:2016-06-23T16:42:26.119Z,chamber has
>> started LOAD operation,R,,,UL,,1077411875,,start_load,1
>> angular.js:12783
>> parseEvents:1:2016-06-23T16:42:26.134Z,/cluster:$1/chmbLLVac:$UL has
>> changed EC "cassette_status". old_value was "unloaded", new_value is
>> "loading",R,,,UL,,900040,,,1
>> angular.js:12783 parseEvents:1:2016-06-23T16:42:26.312Z,Start step 1,
>> "PUMP1", in recipe rcpproc:AKT-CLN-SEA-55K on substrate
>> "NULL_INST_ID",R,,step 1,"PUMP1",CHC,,20002013,,start_step,3
>> angular.js:12783 Get events: 9
>> angular.js:12783 queryEvents eventTime:2016-06-23T16:42:27.562Z
>> angular.js:12783 Thu Jun 23 2016 16:42:27 GMT+0800 (CST)
>>
>>
>>
>> Make database select later
>> 2016-06-23T08:42:26.119Z        "chamber has started LOAD operation"
>>    "R"                        "UL"                "1077411875"
>>    "start_load"        "1"
>> 2016-06-23T08:42:26.134Z        "/cluster:$1/chmbLLVac:$UL has changed EC
>> "cassette_status". old_value was "unloaded", new_value is "loading""
>>  "R"                        "UL"                "900040"
>>      "1"
>> 2016-06-23T08:42:26.135Z        "Start processing material in entry
>> chamber /cluster:$1/chmbLLVac:$UL"        "R"                        "UL"
>>              "1074135052"                        "1"
>> 2016-06-23T08:42:26.145Z        "DOOR_CLOSE TIME:7,
>> CH:/cluster:$1/chmbLLVac:$UL, "Rcp1_Glass465", "Going to Pump, Src/Dest -
>> door_close""        "R"                        "UL"
>>  "1074069515"                        "1"
>> 2016-06-23T08:42:26.16Z        "Chamber finished UNLOAD operation"
>>  "R"                        "LL"                "1077411878"
>>          "2"
>> 2016-06-23T08:42:26.16Z        "/cluster:$1/chmbLLVac:$LL has changed EC
>> "cassette_status". old_value was "unloading", new_value is "unloaded""
>>    "R"                        "LL"                "900040"
>>        "1"
>> 2016-06-23T08:42:26.186Z        "ACLS "ready to unload" for substrate
>> "Rcp1_Glass460""        "R"
>>  "1077411873"                        "2"
>> 2016-06-23T08:42:26.186Z        "ACLS "start unloading" for substrate
>> "Rcp1_Glass460""        "R"
>>  "1077411873"                        "1"
>> 2016-06-23T08:42:26.273Z        "Substrate "Rcp1_Glass461" LEAVE location
>> /cluster:$1/chmbCVD:$CHC <1>"        "R"                        "CHC"
>>  "Rcp1_Glass461"        "1075970059"                "leave_chmb"        "3"
>> 2016-06-23T08:42:26.273Z        "Substrate ID "Rcp1_Glass461", name
>> "/cluster:$1/chmbCVD:$CHC/slotMgr:x/slot:$1", exited slot 1, duration 15632
>> (ms)."        "R"                        "CHC"                "1084817411"
>>                        "2"
>> 2016-06-23T08:42:26.273Z        "SLIT_CLOSE TIME:150,
>> CH:/cluster:$1/chmbCVD:$CHC, "Rcp1_Glass461", "Src - slit_close - Ignore
>> SLIT VALVE CLOSE time. - CloseByTimer.""        "R"
>>  "CHC"                "1074069513"                        "1"
>> 2016-06-23T08:42:26.274Z        "Substrate "Rcp1_Glass461" ENTERED
>> location /cluster:$1/chmbXfer:$1 <1>"        "R"
>>  "TC"        "Rcp1_Glass461"        "1075970058"        "1"
>>  "enter_chmb"        "1"
>> 2016-06-23T08:42:26.312Z        "Data collection STARTED for recipe
>> rcpproc:AKT-CLN-SEA-55K"        "R"                        "CHC"
>>      "1082654742"                        "2"
>> 2016-06-23T08:42:26.312Z        "Start step 1, "PUMP1", in recipe
>> rcpproc:AKT-CLN-SEA-55K on substrate "NULL_INST_ID""        "R"
>>    "step 1,"PUMP1""        "CHC"                "20002013"
>>  "start_step"        "3"
>> 2016-06-23T08:42:26.312Z        "Started recipe rcpproc:AKT-CLN-SEA-55K
>> on substrate "NULL_INST_ID""        "R"        "AKT-CLN-SEA-55K"
>>      "CHC"                "20001023"                "recipe_started"
>>  "1"
>>
>>
>> blue part is not happened in the select.
>>
>> This are the 0.12 influxdb working result.
>>
>> Lee
>>
>>
>> On Mon, Jun 27, 2016 at 5:31 AM, Sean Beckett <[email protected]> wrote:
>>
>>> Points that are in the WAL but haven't yet been flushed to disk should
>>> still be queryable. It sounds like you are getting a partial return,
>>> including points later than the ones that are missing, so it's likely not a
>>> querying after now() issue. Just in case, take a look at
>>> https://docs.influxdata.com/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#querying-after-now
>>> to make sure that's not the issue.
>>>
>>> Can you provide some sample output from the queries, showing the points
>>> "appearing" later?
>>>
>>> What's in the logs during the queries? Any write errors?
>>>
>>> What version of InfluxDB?
>>>
>>> How are you writing points? HTTP API? UDP? Graphite? Telegraf?
>>>
>>> On Fri, Jun 24, 2016 at 9:55 PM, <[email protected]> wrote:
>>>
>>>> Hello,
>>>>
>>>> I meet a problem:
>>>>
>>>> It seems influxdb missing some data when select the times close with
>>>> the written time.
>>>>
>>>> e.g
>>>> The data written is always happen, in every 250ms.
>>>>
>>>> At the time T: 10 points (T1.1, .. T1.10) are written in the influxdb
>>>> at one batch command.
>>>>             T+ 250ms:  10 points (T2.1 ..., T2.10) are written.
>>>>
>>>> At the time T + t (t < 1s), select the points in the T.  select xxx
>>>> where time >= T
>>>>
>>>> I expect: all the 10 points (T1.1 .. T1.10) in the result. But the
>>>> select result is strange.  It only includes partial of 10 points, and some
>>>> later point.
>>>>
>>>> The result is close to T1.1, T1.2, T1.10 (some T1.x are missing), T2.1,
>>>> T2.2 is appeared.  (The data is not lost, it is in the influxdb.)
>>>>
>>>> Is this a reasonable result?  How could I get my expected result: get
>>>> the points the same as written in.
>>>>
>>>> background:  I am using influxdb to a real time monitor.  I try to get
>>>> the real time status.
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> Remember to include the InfluxDB version number with all issue reports
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "InfluxDB" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> Visit this group at https://groups.google.com/group/influxdb.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/influxdb/804e7be3-455c-48ba-98dd-9895a08c1ecc%40googlegroups.com
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Sean Beckett
>>> Director of Support and Professional Services
>>> InfluxDB
>>>
>>> --
>>> Remember to include the InfluxDB version number with all issue reports
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "InfluxDB" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/influxdb/jAGfqUBhpu4/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at https://groups.google.com/group/influxdb.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/influxdb/CALGqCvOOxkGZeQ9ZGwrjLLP63WR10EAjfoA_G0GL4nXEw0GLtQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/influxdb/CALGqCvOOxkGZeQ9ZGwrjLLP63WR10EAjfoA_G0GL4nXEw0GLtQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> Remember to include the InfluxDB version number with all issue reports
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "InfluxDB" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at https://groups.google.com/group/influxdb.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/influxdb/CAO31Sf7jrxoe1D7PQF-BD4zCu7BGASNb1Btcg6y050WK7sTbbg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/influxdb/CAO31Sf7jrxoe1D7PQF-BD4zCu7BGASNb1Btcg6y050WK7sTbbg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Sean Beckett
> Director of Support and Professional Services
> InfluxDB
>
> --
> Remember to include the InfluxDB version number with all issue reports
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "InfluxDB" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/influxdb/jAGfqUBhpu4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/influxdb.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/influxdb/CALGqCvPSWR-Ox9mp78zvX9b%3D8znLK8SzcxDe0jgiYOwcigGUCA%40mail.gmail.com
> <https://groups.google.com/d/msgid/influxdb/CALGqCvPSWR-Ox9mp78zvX9b%3D8znLK8SzcxDe0jgiYOwcigGUCA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/CAO31Sf5EF4QRcYEHojJOdEDzGf4nZas%3Dz86N6-iQDfJ5NkoLkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to