-
Notifications
You must be signed in to change notification settings - Fork 0
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
Heroku - Maximum Storage Size #1
Comments
Is this with or without any data you've extracted for AC? On Thu, Mar 6, 2014 at 3:28 PM, Sunny Juneja [email protected]:
|
With data. On March 6, 2014 at 3:31:00 PM, Sameer S ([email protected]) wrote: Is this with or without any data you've extracted for AC? On Thu, Mar 6, 2014 at 3:28 PM, Sunny Juneja [email protected]:
|
Whoa. How many rows of data are you pushing? On Thu, Mar 6, 2014 at 3:28 PM, Sunny Juneja [email protected]:
|
It really isn't that much. Just 2.2k locations + 1k organizations. I'm sure that number is going to grow by a factor of at least 6 with relatively little work. |
This is really surprising to me -- by default, the setup script ( https://github.com/codeforamerica/ohana-api/blob/master/script/setup_heroku#L31-L32 ) uses the mongo-lab Heroku add-on, and the free tier seems to provide 496mb of storage ( https://addons.heroku.com/mongolab ). @whatasunnyday -- can you run a mongo command to check the storage usage of the "database"? I feel like it shouldn't be anywhere near 496mb yet, but maybe it's from stuff like indexing? Worse comes to worst, the 2gb tier is $15/mo, and OpenOak might have Heroku credits. ( @spjika @eddietejeda -- do we? or is it just AWS?) |
In case the Heroku instance adds too much overhead, let me know - we can On Fri, Mar 7, 2014 at 8:02 AM, Dave Guarino [email protected]:
|
This is actually an Elasticsearch issue. You can see the error is generated after the Elasticsearch index has started:
But still, the error message itself should specify which add-on needs to be upgraded. The Elasticsearch add-on will throw this error when you have the free plan. Upgrading to a paid plan will solve the issue. I need to add this to the documentation, but keep in mind that we are planning on replacing Mongo and Elasticsearch with Postgres over the next month. |
documented upstream |
When pushing to heroku I get the following:
The text was updated successfully, but these errors were encountered: