Ticket #164 (new bug)

Opened 1 week ago

Last modified 5 days ago

QueueUrl "locks" do not prevent many Clients to one QueueUrl

Reported by: mbriggs Assigned to: mbriggs
Priority: high Milestone: 1.1
Component: Drone Version: none
Severity: minor Keywords: queueurl, manager, drone, collision
Cc:

Description

The process of assigning a host_id to a QueueUrl to prevent several clients from retrieving the same url is not effective.

It is possible that multiple requests for new QueueUrls are received by the drone from several managers all at once. The result is that some of the managers may receive one or more QueueUrls that other managers received. This results in duplication of effort among other possible problems.

Attachments

Change History

05/08/08 17:17:55 changed by kindlund

Okay, I've committed an initial fix at r1575 for this issue. Still have to test it out completely.

It seems that Rails built-in validations are only useful if you work with individual records as Rails "objects" — if you try to perform any type of advanced operations (i.e., multi-record SQL updates), then those actions bypass any built-in validations altogether. Performance-wise, this is probably a good thing. However, sanity-wise, it's annoying.

As such, I'm on the fence about whether we should build-out formal validations across all our models. If we do, then we probably should mark each line in the code where we perform low-level SQL queries (so that we can add manual validations as needed).

— Darien

Add/Change #164 (QueueUrl "locks" do not prevent many Clients to one QueueUrl)




Change Properties
Action