Skip to content

Drop amqp workaround#917

Merged
jmchilton merged 1 commit intogalaxyproject:masterfrom
mvdbeek:drop_amqp_workaround
Apr 9, 2019
Merged

Drop amqp workaround#917
jmchilton merged 1 commit intogalaxyproject:masterfrom
mvdbeek:drop_amqp_workaround

Conversation

@mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Apr 3, 2019

If there's no message to be sent there's no activity,
so I don't think this was needed.
If there's a message it should be pretty lightweight too,
I can run 32 processes with a sqlite database and not run into locking
issues when sending messages.

If there's no message to be sent there's no activity,
so I don't think this was needed.
If there's a message it should be pretty lightweight too,
I can run 32 processes with a sqlite database and not run into locking
issues when sending messages.
@mvdbeek mvdbeek requested a review from jmchilton April 9, 2019 12:39
@mvdbeek
Copy link
Member Author

mvdbeek commented Apr 9, 2019

@jmchilton can you have a look at this ? if there are concerns we could also setup a separate sqlite database for the queue.

@jmchilton jmchilton merged commit 4bbae57 into galaxyproject:master Apr 9, 2019
@jmchilton
Copy link
Member

Sorry for the delay, I don't catch PRs not on galaxyproject/galaxy - I need a better workflow. I trust you if you say it isn't a problem, happy to merge. Thanks!

@mvdbeek
Copy link
Member Author

mvdbeek commented Apr 9, 2019

Awesome, thanks!

@mvdbeek mvdbeek deleted the drop_amqp_workaround branch April 9, 2019 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants