X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/ab314b9ea3618c71556a6a5f6dd7c769beaf2737..6c40c1c5b000b2eb0967df0f7ebaf613393501bc:/services/api/config/application.default.yml diff --git a/services/api/config/application.default.yml b/services/api/config/application.default.yml index a5c9de06dd..c2f89582fc 100644 --- a/services/api/config/application.default.yml +++ b/services/api/config/application.default.yml @@ -46,28 +46,16 @@ common: # to log in. workbench_address: false - # The ARVADOS_WEBSOCKETS environment variable determines whether to - # serve http, websockets, or both. + # Client-facing URI for websocket service. Nginx should be + # configured to proxy this URI to arvados-ws; see + # http://doc.arvados.org/install/install-ws.html # - # If ARVADOS_WEBSOCKETS="true", http and websockets are both served - # from the same process. + # If websocket_address is false (which is the default), no websocket + # server will be advertised to clients. This configuration is not + # supported. # - # If ARVADOS_WEBSOCKETS="ws-only", only websockets is served. - # - # If ARVADOS_WEBSOCKETS="false" or not set at all, only http is - # served. In this case, you should have a separate process serving - # websockets, and the address of that service should be given here - # as websocket_address. - # - # If websocket_address is false (which is the default), the - # discovery document will tell clients to use the current server as - # the websocket service, or (if the current server does not have - # websockets enabled) not to use websockets at all. - # - # Example: Clients will connect to the specified endpoint. - #websocket_address: wss://127.0.0.1:3333/websocket - # Default: Clients will connect to this server if it's running - # websockets, otherwise none at all. + # Example: + #websocket_address: wss://ws.zzzzz.arvadosapi.com/websocket websocket_address: false # Maximum number of websocket connections allowed @@ -207,12 +195,10 @@ common: # normally be returned in a single response). # Note 1: This setting never reduces the number of returned rows to # zero, no matter how big the first data row is. - # Note 2: Currently, this only limits the - # arvados.v1.collections.list API (GET /arvados/v1/collections), and - # only takes the size of manifest_text into account. Other fields - # (e.g., "properties" hashes) are not counted against this limit - # when returning collections, and the limit is not applied at all - # for other data types. + # Note 2: Currently, this is only checked against a specific set of + # columns that tend to get large (collections.manifest_text, + # containers.mounts, workflows.definition). Other fields (e.g., + # "properties" hashes) are not counted against this limit. max_index_database_read: 134217728 # Maximum number of items to return when responding to a APIs that @@ -279,6 +265,8 @@ common: # silenced by throttling are not counted against this total. crunch_limit_log_bytes_per_job: 67108864 + crunch_log_partial_line_throttle_period: 5 + # Attributes to suppress in events and audit logs. Notably, # specifying ["manifest_text"] here typically makes the database # smaller and faster. @@ -369,6 +357,27 @@ common: assign_node_hostname: compute%d + ### + ### Job and container reuse logic. + ### + + # Include details about job reuse decisions in the server log. This + # causes additional database queries to run, so it should not be + # enabled unless you expect to examine the resulting logs for + # troubleshooting purposes. + log_reuse_decisions: false + + # Control job reuse behavior when two completed jobs match the + # search criteria and have different outputs. + # + # If true, in case of a conflict, reuse the earliest job (this is + # similar to container reuse behavior). + # + # If false, in case of a conflict, do not reuse any completed job, + # but do reuse an already-running job if available (this is the + # original job reuse behavior, and is still the default). + reuse_job_if_outputs_differ: false + ### ### Remaining assorted configuration options. ### @@ -413,8 +422,6 @@ common: # "git log". source_version: false - crunch_log_partial_line_throttle_period: 5 - # Enable asynchronous permission graph rebuild. Must run # script/permission-updater.rb as a separate process. When the permission # cache is invalidated, the background process will update the permission