Firestore hiccups?

[Manish Malik]

Hi,

(I know Firestore is in Beta - but trying to get a confirmation that Firestore team knows about this).

Did Firestore experience some hiccups for a subset of users a few hours back (and still continuing)? A few hours ago, suddenly, the get()s stopped responding for me - the Promise just won't return at all. I opened the console (web) browser, and saw the same behavior - the spinwheel for loading would just keep spinning and not return when I clicked on any data item.

I asked around in the Slack channel, and at least one person responded that it was working fine for them.

Few hours later (now), it has started fine for my account, but another person in Slack is seeing the same issues.

Firebase status page doesn't show any partial service disruption. Is the Firestore team aware of any issues here?

Best,

Manish

[Kato Richardson]

Hi Manish,

We publish all known service disruptions to the status page. No known issues at present.

I'd recommend logging as much as possible and making sure you're handling/logging all errors (use .catch() on your promises) to see if we can get some more detail.

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/40925e45-d7d5-4df4-9fb9-aa111a654ca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[Tim Lai]

Hi Manish,

As I know, If this happens, write a data to the database should resolve it. It's a knowing issue and I hope Firestore team have already fixed it.

Tim

Manish Malik於 2017年10月11日星期三 UTC+8下午12時49分18秒寫道：

[Ben Carter]

Hi Kato,

I just wanted to add a 'me too' to this query. Twice in the past week (and also right now) I have experienced the exact same behaviour as Manish. I'm working with Objective C on iOS. My getDocumentWithCompletion just never seem to return or take a long time to return. When I view the Firestore database in the dashboard, certain collections just show an activity spinner - others are fine. If I come back to it the next day, it will have resolved. It's really frustrating.

I'll add all the error handling I can and report back with anything I find. Appreciate any responses on this.

Thanks,

Ben

On Wednesday, October 11, 2017 at 12:27:33 PM UTC-7, Kato Richardson wrote:

Hi Manish,

We publish all known service disruptions to the status page. No known issues at present.

I'd recommend logging as much as possible and making sure you're handling/logging all errors (use .catch() on your promises) to see if we can get some more detail.

☼, Kato

On Wed, Oct 11, 2017 at 4:48 AM, Manish Malik <dotm...@gmail.com> wrote:

Hi,

(I know Firestore is in Beta - but trying to get a confirmation that Firestore team knows about this).

Did Firestore experience some hiccups for a subset of users a few hours back (and still continuing)? A few hours ago, suddenly, the get()s stopped responding for me - the Promise just won't return at all. I opened the console (web) browser, and saw the same behavior - the spinwheel for loading would just keep spinning and not return when I clicked on any data item.

I asked around in the Slack channel, and at least one person responded that it was working fine for them.

Few hours later (now), it has started fine for my account, but another person in Slack is seeing the same issues.

Firebase status page doesn't show any partial service disruption. Is the Firestore team aware of any issues here?

Best,

Manish

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/40925e45-d7d5-4df4-9fb9-aa111a654ca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ben Carter]

As a quick follow up, I recorded these error messages in the log output while the problem was occurring:

2017-10-12 21:45:52.563 App[1281:411476] <Firebase/Network/ERROR> Encounter network error. Code, error: -1001, Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://play.googleapis.com/log, _kCFStreamErrorCodeKey=-2103, NSErrorFailingURLKey=https://play.googleapis.com/log, NSLocalizedDescription=The request timed out., _kCFStreamErrorDomainKey=4}
2017-10-12 21:45:52.635 App[1281:411541] CFNetwork SSLHandshake failed (-9806)
2017-10-12 21:45:52.664 App[1281:411541] NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9806)
Oct 12 21:45:52  App[1281] <Error>: [Firebase/Core][I-NET901017] <Firebase/Network/ERROR> Encounter network error. Code, error: -1001, Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://play.googleapis.com/log, _kCFStreamErrorCodeKey=-2103, NSErrorFailingURLKey=https://play.googleapis.com/log, NSLocalizedDescription=The request timed out., _kCFStreamErrorDomainKey=4}
Oct 12 21:45:52  App[1281] <Error>: [Firebase/Core][I-COR000020] Error posting to Clearcut: Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://play.googleapis.com/log, _kCFStreamErrorCodeKey=-2103, NSErrorFailingURLKey=https://play.googleapis.com/log, NSLocalizedDescription=The request timed out., _kCFStreamErrorDomainKey=4}, with Status Code: 0

As described before, a few hours later, it's working well again.

[Manish Malik]

It happened again on Sunday (15th Oct ~ 06.30 GMT) and I was able to record a GIF of what I observed in the firebase console: https://cl.ly/3Z3i3H261o2Q/Screen%20recording%202017-10-15%20at%2012.17.27%20PM.gif

Note the absence of any exception logs (I also captured the browser console in that recording) - this is consistent with my JS sdk logs because the API promise never comes back to either then() or catch() at all - it just hangs forever.

The situation is back to normal for me now after few hours (as it happened last time) - but the recording above will give firebase team a glimpse into what we are observing.

Thanks,
Manish

[Ben Carter]

Happening again for me as well right now - Sunday 15th Oct, 2017 9.30pm PST.

[Manish Malik]

Update: It happened again today (~ 8.15 AM GMT). I tried what Tim had mentioned - put a write to the Firestore database, and voila - all the hung get()s suddenly started working. I even got a console.log() statement I had put in a get() which started more than couple of minutes ago.

Weird, but got my development unblocked for the moment.

[Ben Carter]

@Kato, is there any chance that you could confirm this is being looked into please? I'd like to take this to production in the next few weeks but it will be hard to do that if Firestore keeps getting hung up. Thanks.

[Michael Lehenbauer]

Hey all,

Thank you for the additional feedback!  We've been discussing this issue internally and believe we understand the root cause are working on a fix. Unfortunately it will likely take ~2 weeks for the fix to be fully rolled out to production.  For now, as you've noticed, doing a write should "fix" your hung queries, so hopefully that keeps you from being completely blocked.  Feel free to reach out if anybody is still blocked or has additional insight into how they're hitting this issue, etc.

Thanks again for the feedback and sorry for the inconvenience!

-Michael

--

You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/73383de3-2a61-41b9-ae07-b78181ea0da5%40googlegroups.com.

[Ben Carter]

Hi Michael,

Just wanted to say thanks for following up and for giving us the good news. If you could let us know when the fix has been released to production, that would be much appreciated.

Many thanks,

Ben

On Tuesday, October 17, 2017 at 2:48:09 PM UTC-7, Michael Lehenbauer wrote:

Hey all,

Thank you for the additional feedback!  We've been discussing this issue internally and believe we understand the root cause are working on a fix. Unfortunately it will likely take ~2 weeks for the fix to be fully rolled out to production.  For now, as you've noticed, doing a write should "fix" your hung queries, so hopefully that keeps you from being completely blocked.  Feel free to reach out if anybody is still blocked or has additional insight into how they're hitting this issue, etc.

Thanks again for the feedback and sorry for the inconvenience!

-Michael

On Mon, Oct 16, 2017 at 1:43 AM, Manish Malik <dotm...@gmail.com> wrote:

Update: It happened again today (~ 8.15 AM GMT). I tried what Tim had mentioned - put a write to the Firestore database, and voila - all the hung get()s suddenly started working. I even got a console.log() statement I had put in a get() which started more than couple of minutes ago.

Weird, but got my development unblocked for the moment.

On Monday, October 16, 2017 at 3:48:20 AM UTC+5:30, Manish Malik wrote:

It happened again on Sunday (15th Oct ~ 06.30 GMT) and I was able to record a GIF of what I observed in the firebase console: https://cl.ly/3Z3i3H261o2Q/Screen%20recording%202017-10-15%20at%2012.17.27%20PM.gif

Note the absence of any exception logs (I also captured the browser console in that recording) - this is consistent with my JS sdk logs because the API promise never comes back to either then() or catch() at all - it just hangs forever.

The situation is back to normal for me now after few hours (as it happened last time) - but the recording above will give firebase team a glimpse into what we are observing.

Thanks,
Manish

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

[va...@invoiceready.com]

Not sure if this is helpful, but we experienced this yesterday 23-Oct from 1pm PDT to 5:30 PDT and it "magically" fixed itself, not sure if this was due to a random write. We're using the web API/SDK and the one thing we noticed is when we had a code like this:

     var estimate_doc = db.collection("estimates").doc("XXXXX");


            estimate_doc.get().then(function(doc) {
                if (doc.exists) {
                    console.log("Got estimate:", doc.data());
                    var estimate = doc.data();
                    estimate["id"] = doc.id;


                    var contact_doc = db
                        .collection("contacts")
                        .doc("XXXXXX");


                    contact_doc.get().then(function(doc) {
                        console.log("Document:", doc.data());
                        if (doc.exists) {
                            console.log("Document data:", doc.data());
                            var contact = doc.data();
                        } else {
                            console.log("No such document!");
                        }
                    });
                }
            });

While running this the first query would return, but the second would not, then in Chrome dev tools if we put a break point on the line:

contact_doc.get().then(function(doc) {

And held it there paused for ~15 seconds and let it go through it would work every time. Not sure if this is a known part of the bug, but just in case anyone else finds this helpful, thanks!

[Michael Lehenbauer]

Hey all,

Sorry for the delayed update, but the fix for this went out in the last week, so you shouldn't be seeing this issue anymore.  Please holler if you continue seeing issues with queries getting stuck (especially if doing a write "fixes" the issue).

Thanks,

-Michael

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/381ab185-c28a-4d1d-96c8-99d7e6b2ea84%40googlegroups.com.

[l...@nuvopoint.dk]

Hey

We're still getting hung queries, the issue seems to come and go. Can you confirm that the issue was fixed?

Looking at https://stackoverflow.com/questions/46717898/firestore-slow-performance-issue-on-getting-data it seems people are still having problems with it?

Lars

[Michael Lehenbauer]

Hi Lars,

Firestore is a beta product and we're regularly finding / fixing issues. The original issue covered by this thread was fixed, but you may be hitting something new. Can you please contact support with as much detail as you can provide about what you're seeing and what you're expecting?

Thanks!

-Michael

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/8ed4d3e9-7976-4925-8c0c-87f0c3be8bb2%40googlegroups.com.

[l...@nuvopoint.dk]

Will do