Monitoring Binaries Tasks

Track binary transfer progress, failures, and lifecycle states between Federation members.

Binaries tasks track asynchronous binary transfers between Federation members.

Access Binaries Tasks

To access Binaries Tasks:

Open Federation Dashboard.
Select a repository to view connection states.
Select a specific member connection.
Review the binaries tasks panel.

Binaries Tasks Indicators

The following table describes the binaries tasks indicators.

Indicator	Description
In Progress	Number of active binary transfers
Failed	Number of failed binary transfers

Binary Task Lifecycle States

Binary tasks transition through the following states during processing.

Status	Description
AVAILABLE	Task is queued and waiting for a storage handler to pick it up.
IN_PROGRESS	Handler is downloading from source or uploading to target.
COMPLETED	Binary transferred successfully.
DELETED	Task is marked for deletion after successful completion.
EXHAUSTED_SUBMISSION	Maximum retries when submitting to Artifactory are exceeded. Use the Replay Failed Binary Tasks API.
EXHAUSTED_STORAGE	Maximum retries for storage operations are exceeded. Use the Replay Failed Binary Tasks API.
REJECTED	Target Artifactory rejected the binary due to validation or policy checks. Review rejection details in logs.

For state machine diagrams and full details, see Member State Reference.

How Binary Task Processing Works

A metadata event references a binary SHA.
Target member checks local binary presence.
Missing binary creates a task.
Task handler fetches from source and transfers to target.
Success marks task complete. Failures retry up to configured limits.

Key Tuning Properties

The following table lists key properties for tuning binary task handling.

Property	Default	Description
`rtfs.binary.tasks.max.retry.per.task`	10	Max retries per task
`rtfs.binary.tasks.handler.tenants.thread.pool.size`	100	Worker pool size
`rtfs.binary.tasks.handler.fetch.limit.per.tenant`	500	Max tasks fetched per tenant run
`rtfs.binary.tasks.inbound.insert.batch.size`	500	Insert batch size
`rtfs.binary.tasks.handler.initial.delay.duration`	PT1M	Initial delay before handler starts
`rtfs.binary.tasks.handler.run.duration`	PT1S	Handler run interval

Troubleshooting Signals

High In-Progress Count

Usually indicates heavy transfer load.
Validate network throughput between members.
Consider increasing worker pool size.

High Failed Count

Validate member connectivity and credentials.
Verify source binary availability.
Review RTFS logs and retry configuration.

Tasks Not Progressing

Confirm task handler is running.
Check queue penalties and retry state.
Trigger manual recovery or Full Sync if needed.

Frequently Asked Questions

This section provides answers to frequently asked questions about Binaries Tasks.

plusFAQs

Q: How do I view binaries tasks for a Federated repository?

A: Open the Federation Dashboard, select a repository to view connection states, select a specific member connection, then review the binaries tasks panel. See Access Binaries Tasks for details.

Q: What is the difference between EXHAUSTED_SUBMISSION and EXHAUSTED_STORAGE?

A: EXHAUSTED_SUBMISSION means the maximum retries for submitting the task to Artifactory were exceeded. EXHAUSTED_STORAGE means the maximum retries for the storage operation itself were exceeded. Both require the Replay Failed Binary Tasks API to retry.

Q: What should I check if binary tasks are not progressing?

A: Confirm the task handler is running, check queue penalties and retry state, and trigger manual recovery or Full Sync if needed. See Tasks Not Progressing for the full checklist.

Q: How many times will a binary task retry before it's marked exhausted?

A: Retries are controlled by the rtfs.binary.tasks.max.retry.per.task property, which defaults to 10 retries per task.

Q: What causes a binary task to be REJECTED?

A: A task is REJECTED when the target Artifactory rejects the binary due to validation or policy checks. Review the rejection details in your logs.