Skip to main content

Skipping Blob Repository Mismatch Task Processing During Upgrade to 3.90.3 or Later

Updated

Overview

Starting in Nexus Repository 3.90.3, a skip option is available for the BlobRepositoryMismatchTask ( repository.blob.mismatch.task ) to let eligible customers bypass blob properties value mismatch processing during upgrade.

This option is intended for specific upgrade paths where mismatch scanning is not expected to be needed. When used in the correct circumstances, it avoids unnecessary blob scanning, reduces upgrade time, limits excess blob storage API calls, and helps prevent resource contention on unaffected nodes.

When this applies

This skip option applies only when all of the following are true:

  • The instance is being upgraded directly from a version earlier than 3.69
  • The target version is 3.90.3 or later
  • The deployment does not expect blob store mismatch conditions that require processing
  • The property is set on each node before the upgrade begins

This is not a general-purpose performance setting. It should only be used for the specific upgrade scenario described above.

Why this skip option was added

The skip option was added to address cases where customers upgrading directly from versions earlier than 3.69 to 3.90.3 or later would otherwise trigger blob mismatch processing even when no mismatches are expected.

In those cases, running the task provides no practical benefit but can still add upgrade overhead. That overhead may include:

  • Additional blob scanning
  • Excess S3 API calls
  • Longer upgrade time
  • Resource contention across unaffected nodes

The skip option gives operators a controlled way to avoid that overhead when the conditions are known and understood.

Why the Blob Repository Mismatch Task exists

The BlobRepositoryMismatchTask upgrade step was introduced to detect and fix blob repository mismatch conditions that can arise as a result of primarily staging move operations. Its purpose is to ensure the system can identify and handle situations where recorded state inside blob properties files and database records may not be aligned.

In other words, the task exists to protect repository integrity in upgrade or operational scenarios where reconciliation processing may be required.

For environments where such mismatches are not expected, and only for the qualifying direct upgrade path described above, the skip option allows operators to bypass that processing safely.

How to enable the skip option

Before upgrading each node to Nexus Repository 3.90.3 or later, add the following property to the nexus.properties file on each node in the repository instance:

blob.repository.name.mismatch.skipProcessing=true

After saving the change, proceed with the upgrade as planned.

Important requirements

  • The property must be set before upgrading to 3.90.3 or later
  • The property must be added to the nexus.properties file on each node
  • Processing should ONLY be skipped for direct upgrades from versions earlier than 3.69
  • Processing should ONLY be skipped under high confidence that blob repository mismatches are NOT expected

When not to use this option

Do not use this option in the following cases:

  • Upgrades that do not start from a version earlier than 3.69
  • Upgrades where blob mismatch processing is expected or required
  • Situations where the repository state or historical upgrade activity is uncertain and mismatch detection should still run

If there is any reason to believe mismatch processing may be needed, do not enable the skip option.

Related to

Related articles