Hi Roger
There is some logic in TS v3 to retry execute calls when these errors crop up -
but I'd made a typo in the deletion logic and skipped that. I've just pushed a
fix to sort that out:
https://github.com/pat/thinking-sphinx/commit/0c404e756d037daeae579736b4248e963fa3ef01
You can give it a spin with the following in your Gemfile:
gem 'thinking-sphinx', '~> 3.0.4',
:git => 'git://github.com/pat/thinking-sphinx.git',
:branch => 'master',
:ref => '0c404e756d'
Sorry for the hassle!
--
Pat
On 21/07/2013, at 6:40 PM, Roger Kind Kristiansen wrote:
> Hi,
>
> I recently upgraded fra TS2 to TS3, and everything seemed to be working
> nicely. Then I noticed the following errors popping up in New Relic from
> production:
>
> ThinkingSphinx::QueryExecutionError: closed MySQL connection
> OtherTransaction/DelayedJob#Thinking Sphinx: Mark 1084 in doctor_core as
> deleted
>
> With the following stack trace:
>
> …hinking-sphinx-3.0.4/lib/thinking_sphinx/connection.rb: 75:in `rescue in
> execute'
> …hinking-sphinx-3.0.4/lib/thinking_sphinx/connection.rb: 71:in `execute'
> …-sphinx-3.0.4/lib/thinking_sphinx/deltas/delete_job.rb: 8:in `block in
> perform'
> …undle/ruby/1.9.1/gems/innertube-1.0.2/lib/innertube.rb: 127:in `take'
> …-sphinx-3.0.4/lib/thinking_sphinx/deltas/delete_job.rb: 7:in `perform'
> …ing_sphinx/deltas/delayed_delta/flag_as_deleted_job.rb: 27:in `perform'
> …s/delayed_job-ceb64874fc42/lib/delayed/backend/base.rb: 94:in `block in
> invoke_job'
> …gems/delayed_job-ceb64874fc42/lib/delayed/lifecycle.rb: 60:in `call'
> …gems/delayed_job-ceb64874fc42/lib/delayed/lifecycle.rb: 60:in `block in
> initialize'
> …gems/delayed_job-ceb64874fc42/lib/delayed/lifecycle.rb: 65:in `call'
> …gems/delayed_job-ceb64874fc42/lib/delayed/lifecycle.rb: 65:in `execute'
> …gems/delayed_job-ceb64874fc42/lib/delayed/lifecycle.rb: 38:in `run_callbacks'
> …s/delayed_job-ceb64874fc42/lib/delayed/backend/base.rb: 91:in `invoke_job'
> …er/gems/delayed_job-ceb64874fc42/lib/delayed/worker.rb: 182:in `block (2
> levels) in run'
> <snip>
>
> It's all running on Heroku with postgres, so I guess this is the connection
> to the sphinx server failing for some reason. It only seems to happen for the
> delayed deltas and seems to be pretty consistent, in that the same mark value
> causes several consecutive errors.
>
> I haven't been able to reproduce this locally, so I'm just wondering if
> someone else have seen this and what might be done to correct it?
>
> thinking-sphinx 3.0.4
> flying-sphinx 1.0.0
> mysql2 0.3.12b4
>
> Cheers,
> Roger
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Thinking Sphinx" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/thinking-sphinx.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
You received this message because you are subscribed to the Google Groups
"Thinking Sphinx" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/thinking-sphinx.
For more options, visit https://groups.google.com/groups/opt_out.
