From 8a810387012088dd051f1be6fd4e7c38282e9df8 Mon Sep 17 00:00:00 2001 From: Nate Coraor Date: Tue, 19 Apr 2022 14:28:01 -0400 Subject: [PATCH 1/2] Add an option to disable searching for distributed object store datasets that don't have an object_store_id --- .../sample/object_store_conf.xml.sample | 8 ++++++- lib/galaxy/model/__init__.py | 12 ++++++++-- lib/galaxy/objectstore/__init__.py | 23 +++++++++++-------- 3 files changed, 31 insertions(+), 12 deletions(-) diff --git a/lib/galaxy/config/sample/object_store_conf.xml.sample b/lib/galaxy/config/sample/object_store_conf.xml.sample index 401e27a4655..db5163a46a7 100644 --- a/lib/galaxy/config/sample/object_store_conf.xml.sample +++ b/lib/galaxy/config/sample/object_store_conf.xml.sample @@ -59,10 +59,16 @@ In distributed and hierarchical world, you can choose that some backends are automatically unused whenever they become too full. Setting the maxpctfull - attribute (on top level object_store it behaves as a global default) enables + attribute (on top level backends tag it behaves as a global default) enables this, or it can be applied to individual backends to override a global setting. This only applies to disk based backends and not remote object stores. + + By default, if a dataset should exist but its object_store_id is null, all + backends will be searched until it is found. This is to aid in Galaxy + servers moving from non-distributed to distributed object stores, but this + behavior can be disabled by setting search_for_missing="false" on the top + level backends tag. -->