yeah you are right, but it is really hard to replicate it because lot of stuff is involved. Anyway, since my queues work on same rows, I guess this is the problem. Anche with the new design, problem never occurs, so I guess this was the case.
Thanks! On Monday, 9 January 2017 16:59:14 UTC+1, Jeremy Evans wrote: > > On Monday, January 9, 2017 at 7:20:01 AM UTC-8, Nicolò Benigni wrote: >> >> I am having strange behaviour when running some operations on concurrent >> (that runs in parallels, in separate processes) Resque (github gem) queues. >> When 2 queues are making their operations on the same lines in DB, I get >> strange errors, always differents from the Sequel. Most of the times are >> Validation errors (from the plugin Sequel validations) that are false (e.g. >> email_address exists, but it is not true), and other times are errors >> directly from Sequel internals (Object does not exist). >> >> I think that in my particular case can happen race condition, and would >> like to know if my intuition are right. >> >> I have changed the design of my code to avoid to execute the operations >> in parallels, and everything goes right, so I presume I am on the right >> path. >> > > Well, without a self contained example, it's hard to guess at what the > problem might be. But in general, parallel operations can cause issues if > they modify the same rows that are being modified concurrently by other > threads/processes. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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 https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
