Member State Reference

This reference provides an exhaustive list of member states, queue states, and related status enums used by Federated repositories.

Member State Machine

Federation members transition through lifecycle states while RTFS performs queue processing, full sync, and recovery operations.

stateDiagram-v2
    [*] --> PENDING_FS: New member or full sync required
    PENDING_FS --> FULL_SYNC_PREPARING: Full sync starts
    FULL_SYNC_PREPARING --> FULL_SYNC_RUNNING: File list prepared
    FULL_SYNC_RUNNING --> HEALTHY: Sync completed

    HEALTHY --> ERROR_GENERIC: Processing error
    HEALTHY --> ERROR_INACTIVE: Target unreachable
    HEALTHY --> ERROR_OUT_OF_SYNC: Missing purged events

    ERROR_GENERIC --> HEALTHY: Auto-heal or retry succeeded
    ERROR_INACTIVE --> HEALTHY: Connectivity restored
    ERROR_OUT_OF_SYNC --> PENDING_FS: Full sync required

    HEALTHY --> READ_ONLY: Receiver-only mode enabled
    READ_ONLY --> HEALTHY: Bi-directional sync restored

    classDef component fill:#41b375,stroke:#389b65,color:#fff
    class PENDING_FS,FULL_SYNC_PREPARING,FULL_SYNC_RUNNING,HEALTHY,READ_ONLY component

Member States

Federation members can be in the following states.

Priority ordering: lower values indicate healthier states. Overall repository status uses the most severe state across members.

UI Dashboard States

The dashboard displays the following state keys.

Dashboard Status Mapping

The Federation dashboard displays simplified labels that map to RTFS member states.

Member Queue States

The MemberQueueState enum defines the following queue states.

Heartbeat Status

Heartbeat checks return the following statuses.

Full Sync Phase

Full Sync operations progress through the following phases.

Binary Task State Machine

When RTFS propagates a CREATE or UPDATE event, binary content may not exist on the target. RTFS creates a binary task to transfer that content.

stateDiagram-v2
    [*] --> AVAILABLE: Event requires binary

    AVAILABLE --> IN_PROGRESS: Storage handler picks up task
    IN_PROGRESS --> COMPLETED: Binary transferred successfully
    IN_PROGRESS --> AVAILABLE: Transient failure, retry
    IN_PROGRESS --> EXHAUSTED_SUBMISSION: Max Artifactory retries exceeded
    IN_PROGRESS --> EXHAUSTED_STORAGE: Max storage retries exceeded
    IN_PROGRESS --> REJECTED: Binary rejected by target

    COMPLETED --> DELETED: Task cleanup
    DELETED --> [*]

    EXHAUSTED_SUBMISSION --> AVAILABLE: Manual replay triggered
    EXHAUSTED_STORAGE --> AVAILABLE: Manual replay triggered
    REJECTED --> [*]: Task cannot be retried

    classDef component fill:#41b375,stroke:#389b65,color:#fff
    classDef secondary fill:#ffffff,stroke:#41b375,color:#41b375
    class AVAILABLE,IN_PROGRESS,COMPLETED component
    class DELETED,EXHAUSTED_SUBMISSION,EXHAUSTED_STORAGE,REJECTED secondary

Binary Task Status Reference

The following table describes each binary task status.

Monitoring Binary Tasks

Use these metrics to monitor binary task health. In Prometheus or Grafana, query the scraped names (see Open Metrics Reference):

• jfrtfs_binary_tasks_total_count_by_status_total: Counter for binary task counts by status. The logical name is jfrtfs_binary_tasks_total_count_by_status. Exposition typically adds the _total suffix.
• jfrtfs_binary_tasks_handler_execution_duration_millis: Timer and histogram family. Series may include _count, _sum, _bucket, or related suffixes depending on export.

For example, a PromQL query against the counter metric:

jfrtfs_binary_tasks_total_count_by_status_total

Which Artifactory Version Includes Which RTFS Fixes

Self-hosted JPDs run Artifactory together with the Artifactory Federation Service (RTFS). Each Artifactory self-managed release bundles a specific RTFS build. Use the following table to see which RTFS version ships with common Artifactory release lines.

Patch releases within the same Artifactory line can ship a newer RTFS build. For the exact RTFS version at your patch level, check Artifactory self-managed release notes or the Federation topics in this documentation set (for example, Federation over JFrog Bridge).

Check what you're running:

1. Note your Artifactory version (Administration UI, installer, or Helm release).
2. Use this reference to find the RTFS line bundled with your release, or confirm the exact version in release notes.
3. If RTFS is enabled, confirm the service is healthy. See Verify RTFS is running.

Binary sync when a Federation member is down

If one Federation member is offline, other members should still be able to fetch missing binaries from the rest of the Federation. That behavior is fixed in Artifactory 7.128.0 or later. Contact JFrog Support if you're on an earlier release and need this fix on your upgrade path.

This behavior applies only when RTFS is enabled. It does not apply to legacy Federation (RTFS disabled). If your environment still uses legacy Federation, migrate to RTFS and upgrade to a release that includes the fix.

Related Topics

• Federation Dashboard
• Monitoring Connection States
• Monitoring Binaries Tasks
• Troubleshooting Guide