Are you continuously running this instance and just restarting it or do you
start a clean instance each time?
I'd suggest ensuring the persistent_data.yaml in your cluster's bucket is
correct (see below), terminating this instance, and starting a new one with
the same user data as used for this
I have never setup a Galaxy instance fronting multiple clusters, but it's
something I would like to explore. I have a dedicated cluster to run Galaxy
jobs and I've got another a shared cluster to which I hope Galaxy can assign
jobs when the dedicated cluster is too busy.
From my understanding of
A fix for these warnings is in revision 6048 of galaxy-central -
again, thanks for pointing them out Michael.
For the record, the warnings were from the HSmetrics and GCbias tools
and arose because there is a user configurable maxheap parameter that
is not available by default - it is commented
