commit/galaxy-central: dannon: Remove set_metadata_externally from the universe sample.
1 new commit in galaxy-central: https://bitbucket.org/galaxy/galaxy-central/commits/10a0ad2f0280/ Changeset: 10a0ad2f0280 User: dannon Date: 2013-05-06 19:07:31 Summary: Remove set_metadata_externally from the universe sample. Affected #: 1 file diff -r b72a06cf0247ac266fb7b2fc204cef7fb4691cb0 -r 10a0ad2f0280cb044bde1e6424b7a7a93365d5ce universe_wsgi.ini.sample --- a/universe_wsgi.ini.sample +++ b/universe_wsgi.ini.sample @@ -625,12 +625,6 @@ # running more than one Galaxy server using the same database. #enable_job_recovery = True -# Setting metadata on job outputs to in a separate process (or if using a -# cluster, on the cluster). Thanks to Python's Global Interpreter Lock and the -# hefty expense that setting metadata incurs, your Galaxy process may become -# unresponsive when this operation occurs internally. -#set_metadata_externally = False - # Although it is fairly reliable, setting metadata can occasionally fail. In # these instances, you can choose to retry setting it internally or leave it in # a failed state (since retrying internally may cause the Galaxy process to be Repository URL: https://bitbucket.org/galaxy/galaxy-central/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email.
participants (1)
-
commits-noreply@bitbucket.org