tag:support.flying-sphinx.com,2011-01-05:/discussions/problems/780-cant-index-or-rebuild-after-a-dbresetFlying Sphinx: Discussion 2016-08-11T01:32:43Ztag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T16:28:24Z2013-05-30T16:28:31ZCan't index or rebuild after a db:reset<div><p>Update:</p>
<p>It looks like db:reset doesn't work on heroku, because of
permissions.</p>
<p>Tried again with pg:reset and db:setup, and the problem still
exists.</p></div>Corbintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T16:43:30Z2013-05-30T16:43:32ZCan't index or rebuild after a db:reset<div><p>just ran</p>
<blockquote>
<blockquote>
<p>heroku run bundle exec flying-sphinx configure</p>
</blockquote>
</blockquote>
<p>And got the output...</p>
<p>Connecting to database specified by DATABASE_URL<br>
W, [2013-05-30T16:41:42.166902 #2] WARN -- : Action timed out. If
this is happening regularly, please contact Flying Sphinx support:
<a href=
"http://support.flying-sphinx.com">http://support.flying-sphinx.com</a><br>
I, [2013-05-30T16:41:42.167176 #2] INFO -- : Action Finished:
configure</p></div>Corbintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T16:51:38Z2013-05-30T16:51:40ZCan't index or rebuild after a db:reset<div><p>I have also been unable to index flying-sphinx on Heroku for the
last 12 hours. Same problem of freezing. I'm not sure whether it's
related, but maybe there's a more systematic problem going on?</p></div>Sandi Lintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T16:56:25Z2013-05-30T16:56:26ZCan't index or rebuild after a db:reset<div><p>@Sandi Thanks for the comment. I'll stop beating my head against
the wall until I hear from Pat on this. :)</p>
<p>I also reinstalled flying sphinx, with no luck. I'm out of
ideas...</p></div>Corbintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T18:29:11Z2013-05-30T18:29:13ZCan't index or rebuild after a db:reset<div><p>I'm getting as far as rotating indices now:<br>
rotating indices: successfully sent SIGHUP to searchd</p>
<p>But still not completing.</p></div>Sandi Lintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T21:00:41Z2013-05-30T21:00:41ZCan't index or rebuild after a db:reset<div><p>Magic! It's working now.</p>
<p>@FlyingSphinx why did this happen?</p>
<p>BTW I'm running wooden on vienna</p></div>Corbintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T21:07:00Z2013-05-30T21:07:01ZCan't index or rebuild after a db:reset<div><p>That's good to hear. Mine is still freezing. I'm also using
wooden.</p></div>Sandi Lintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T21:17:09Z2013-05-30T21:17:09ZCan't index or rebuild after a db:reset<div><p>Correction: seems to be working but is very slow and
occasionally still times out.</p></div>Sandi Lintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-30T23:42:24Z2013-05-30T23:42:24ZCan't index or rebuild after a db:reset<div><p>Hi Sandi, Corbin</p>
<p>Still investigating to find the cause, but there was something
causing a significant backlog with job processing (which all
actions go through - and normally there's no backlog at all!). If
indexing is still timing out or slow, do let me know, because I'd
like to get this sorted.</p>
<p>I'll continue to hunt through logs and New Relic data to see if
I can figure out the original cause though.</p>
<p>Kind regards,</p>
<p>Pat Allan</p></div>Pat Allantag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-31T00:16:24Z2013-05-31T00:16:24ZCan't index or rebuild after a db:reset<div><p>Thanks Pat for looking into it! Good luck!</p></div>Sandi Lintag:support.flying-sphinx.com,2011-01-05:Comment/270806332013-05-31T00:40:40Z2013-05-31T00:40:40ZCan't index or rebuild after a db:reset<div><p>It's a bit hard to tell - New Relic and logging provide some
clues, but here's what I think happened:</p>
<ul>
<li>Someone signed up for Flying Sphinx and then created an
enormous amount of index requests (not great for the queue).</li>
<li>They then removed their account - which meant the index
requests kept looking for the account, failed, and were retrying
(also not great for the queue).</li>
</ul>
<p>This hurt the service for everyone else, so here's what's
changing:</p>
<ul>
<li>If accounts are removed, index requests (and other actions)
will fail gracefully and not retry (already in production!).</li>
<li>I'm considering implementing rate limiting for indexing…
adds a bit more overhead though, but maybe there's a way that it
can happen outside the API HTTP requests, to keep them snappy.</li>
</ul>
<p>But again: if you're still having issues (or anything else crops
up in the future), do let me know.</p>
<p>I appreciate your patience!</p></div>Pat Allan