From 68065e123800a5a2e700d636db9354702ac42fe5 Mon Sep 17 00:00:00 2001 From: Dannon Baker Date: Mon, 6 May 2013 13:07:31 -0400 Subject: [PATCH] Remove set_metadata_externally from the universe sample. --- universe_wsgi.ini.sample | 6 ------ 1 file changed, 6 deletions(-) diff --git a/universe_wsgi.ini.sample b/universe_wsgi.ini.sample index d474d526c5f..8e1668e6340 100644 --- a/universe_wsgi.ini.sample +++ b/universe_wsgi.ini.sample @@ -625,12 +625,6 @@ use_interactive = True # 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