a.com
December 13, 2016, 2:36pm
1
Every now and then my database connection will timeout. I have one large collection with 5M records, I’m not sure if this is causing some kind of issue. It is also taking awhile for the initial query, even though it has a limit of 30 records on it.
I’ve found some threads that are similar, but still not sure the answer here (or the possible answers at least):
What happens to Meteor during a MongoDB failover event?
I’m also interested in this as I also just updated my mongo version (to 3.0.8). The process causes the primary to failover, it updates the primary and then restarts it. During the process my logs filled up with exceptions from observe. Not finding the primary is hardly cause for an exception is it ? What happens if the primary fails for any long period of time ?
In my case I’m using Kadira so not sure if their wrapper around it has anything do with it. Certainly doesn’t look like it.
Internal …
Collection query exception fails with error on “meteor_accounts loginServiceConfiguration”
What mongo permission does the collection need. I tried createIndex,listIndexes,find,remove,update,insert. But all lead to
Exception from sub meteor.loginServiceConfiguration id 123 Error: Exception while polling query {"collectionName":"meteor_accounts_loginServiceConfiguration","selector":{},"options":{"transform":null,"fields":{"secret":0}}}: not authorized for query on db.meteor_accounts_loginServiceConfiguration
while reloading the page.
Why does it get queried at all? I only use account…
Problems with database connection
HI,
We’re struggling with a very strange error on our production instance. It seems that our app looses connection to it’s mongo database and cannot connect to it. We’re deployed on modulus.io , running on a single servo for now, we have had the issue with various versions of meteor (right now we’re on 1.3.3.1). Restarting the project helps for a few hours. What helped for longer time is setting up a new database in modulus and migrating our data to it and then switching connect string. Still af…
Mongo corrupted data maybe Ground db it is causing this
We are experimenting a problem, we have our app hosted in modulus, when we deploy a new release, arbitrarily they begin to generate documents in different collections with ids that can be json objects with one property or dates , which causes the application to start throwing the error i mention above. After researching about it and did not find any solution beginning to believe that the error may be caused when the javascript code of the application is updated while even local database is synch…
Meteor.publish() - how to get documents by free text
I trying to get documents by free text.
This part, that getting data by field works OK and returns data:
Meteor.publish("messages", function(){
return Messages.find({ discussion_id: "discus_id_87" });
});
This one doesn’t work:
Meteor.publish("messages", function(){
return Messages.find({ $text: { $search: "Some text" } });
});
Returns an ERROR:
Error: Exception while polling query {"collectionName":"messages","selector":{"$text":{"$search":"Some text"}},"options":{"transform":nul…
I’m hoping the data isn’t corrupted. Is there anyway to determine if the data is corrupted?
y01s
January 26, 2017, 11:17am
2
In your case (a collection with a huge amount of documents) I guess you’d better use indexes, because they really reduce the query time. https://docs.mongodb.com/manual/indexes/
Mongodb database profiling may help in finding the queries that take a lot of time, thus making your app slow https://docs.mongodb.com/manual/administration/analyzing-mongodb-performance/#database-profiling
I had the same problem lately. But I found out that it was (mainly) due to a mistake a made in the code.
My meteor app is deployed in a EC2 instance (t2.nano) using mupx.
It has been running just fine since July, but one day in December, it just stopped working, I’ve restarted the instance, and it worked again.
Two weeks later, the same thing happened, restart instance.
But this sunday, it stopped working a lot of times, and even after I restarted the instances, the problems occured after a few minutes .The app did actually get a big amout of traffic compared to the other days, but I don’t belie…