-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.4.0.1] Error: key $lt must not start with '$' #7594
Comments
Can you provide a full reproduce with code, not only the error message? It's hard to guess what did you write through a error message. |
I'm seeing something similar: it's coming from a query of the form |
The line that triggers this appears to be
in pendingCredentials.js. It seems that somehow this |
In @brianlukoff's case it is an update turning into an insert. @brianlukoff reported this to Galaxy support and I saw in that report that there were other things in the stack trace like matb33:collection-hooks and aldeed:collection2-core, and upserts are strangely similar to inserts. But in this case it's just a remove and those packages are not in the stack trace. @WayneUong can you share with us the contents of your |
This is my current
|
There seem to be a large number of packages here that tweak how collections work (collection hooks, etc). Is this issue easily reproducible for you? Can you pare down your app bit by bit (removing packages, etc) to see which packages are required to see this issue? |
I have neither encountered nor been able to reproduce this error again. We have a very large app and narrowing down which module that caused this isn’t possible. I just saw it once in the server log and posted it here to see if anyone saw this too.
|
We are also not able to reproduce in dev, although in our case it is happening pretty consistently (and randomly) in production). |
This error persists even after using .direct to bypass collection-hooks:
|
@WayneUong - can I ask which database provider you are using? |
We’re using ScaleGrid.io http://scalegrid.io/
|
Managed to hunt it down: mongodb-js/mongodb-core#121. The issue only happens when you have connection issues. I'll do a release of |
This was a fairly serious issue with the mongo driver
Fantastic - thanks @tmeasday ! Is it possible for us to utilize the new version of |
@brianlukoff yes, you can update with |
I'm getting |
@brianlukoff what version do you have in That error is kind of annoying. If you temporarily add |
(Also did you try in the last 5 minutes? I just published it) |
Weird - when I added |
@tmeasday Possible to bump one more time, to 2.2.8? See https://twitter.com/christkv/status/768037962064007168 |
Sure, try |
Thanks for this @tmeasday. We've been seeing a flurry of these I'll do some stress testing and see if we still encounter the error after updating. |
Thanks @tmeasday ! |
@tmeasday It looks like there is something wrong with 2.2.8 - upon deploy our query times skyrocketed for both publications and methods. We redeployed with 2.2.7 and things went back to normal. (We are using 3.2 with WT on Compose.) |
Hmm, thanks for the heads up. Let's watch this space carefully (perhaps we'll see another release of the driver soon). I'm not sure if I should do a 1.4.1.2 Mongo release to address this (and revert to the 2.2.7 driver), or wait for a 2.2.9. :/ For anyone else concerned by this, you can get the 2.2.7 driver in
|
We'd love to test 2.2.8 with our staging db as well, but we lack the tools to monitor query times. @brianlukoff what do you guys use to monitor your db? Do you have a set of standard tests for query times comparison? We're using 3.2 WT on EC2, managed by scalegrid. |
@WayneUong We are using Kadira to monitor. It was clear once we deployed 2.2.8 that it was an issue - publication and method response times jumped 5-10x. |
@tmeasday 2.2.9 is released to fix the performance issue (https://jira.mongodb.org/browse/NODE-803). Possible to bump the version again? |
@brianlukoff -- sure, I'll get it out today |
Thanks @tmeasday ! |
By "today" yesterday, it turns out I meant "tomorrow". |
To follow up on this, we haven't seen the "key _ must start with $" error since updating to 1.5.47. Thanks! |
Thanks @tmeasday - I can confirm we haven't seen the issue this thread is about either with 1.5.47 - I'm hoping that 2.2.9 will resolve some other database connection issues we're having. |
I think we can close this one. I won't do a specific Meteor release for the new |
The text was updated successfully, but these errors were encountered: