| ISPN000202 |
Encountered issues while backing up data for cache %s to site %s |
WARN |
This message indicates an issue has occurred with state transfer operations. First
check that the site is online and if any network issues have occurred. Confirm that
the relay nodes in the cluster are not overloaded with cross-site replication requests.
In some cases garbage collection pauses can also interrupt backup operations. You
can either increase the amount of memory available to relay nodes or increase the
number of relay nodes in the cluster. |
| ISPN000289 |
Cannot send cross-site state chunk to '%s'. |
WARN |
During a state transfer operation it was not possible to transfer a batch of cache
entries. First check that the site is online and if any network issues have occurred.
Confirm that the relay nodes in the cluster are not overloaded with cross-site replication
requests. In some cases garbage collection pauses can also interrupt backup operations.
You can either increase the amount of memory available to relay nodes or increase
the number of relay nodes in the cluster. |
| ISPN000291 |
Cannot apply cross-site state chunk. |
WARN |
During a state transfer operation it was not possible to apply a batch of cache entries.
Ensure that sites are online and check network status. |
| ISPN000322 |
Cannot restart cross-site state transfer to site %s |
WARN |
It was not possible to resume a state transfer operation to a backup location. Ensure
that sites are online and check network status. |
| ISPN000337 |
Backup configuration must include a 'site'. |
EXCEPTION |
Caches that use cross-site replication must include a site in the configuration. Edit
the cache and specify the name of the site in the backup configuration. |
| ISPN000338 |
You must specify a 'failure-policy-class' to use a custom backup failure policy for
backup '%s'. |
EXCEPTION |
The backup configuration for the cache uses a custom failure policy but does not include
the fully qualified class of a custom failure policy implementation. Specify the failure
policy class in the backup configuration or use a different failure policy. |
| ISPN000339 |
Remote cache name is missing or null in backup configuration. |
EXCEPTION |
Cross-site replication backs up data to caches with the same name by default. If you
want to backup to a cache with a different name, you must specify the name of the
remote cache in the 'backup-for' configuration. Modify cache configuration to include
the name of the remote cache. |
| ISPN000340 |
Remote cache name and remote site is missing or null in backup configuration. |
EXCEPTION |
Cross-site replication backs up data to caches with the same name by default. If you
want to backup to a cache with a different name, you must specify the name of the
remote cache and the remote site in the 'backup-for' configuration. Modify cache configuration
to include the name of the remote cache and remote site. |
| ISPN000400 |
Node %s was suspected |
EXCEPTION |
A node in the cluster is offline or cannot be reached on the network. If you are using
cross-site replication this message indicates that the relay nodes are not reachable.
Check network settings for all nodes in the cluster. |
| ISPN000439 |
Received new cross-site view: %s |
INFO |
A cluster has either joined or left the global cluster view. |
| ISPN000446 |
Multiple sites have the same name '%s'. This configuration is not valid. |
EXCEPTION |
The name for each cluster that participates in cross-site replication must have a
unique site name. Modify JGroups RELAY2 configuration and specify a unique site name
for each backup location. |
| ISPN000449 |
Timeout value for cross-site replication state transfer must be equal to or greater
than one. |
EXCEPTION |
The value of the timeout attribute is zero or a negative number. Specify a value of
at least one for the timeout attribute in the cross-site state transfer configuration
for your cache. |
| ISPN000450 |
Wait time between retries for cross-site replication state transfer must be equal
to or greater than one. |
EXCEPTION |
The value of the wait-time attribute is zero or a negative number. Specify a value
of at least one for the wait-time attribute in the cross-site state transfer configuration
for your cache. |
| ISPN000477 |
Cannot perform operation %s for site %s |
ERROR |
It was not possible to successfully complete an operation on a backup location. Set
logging levels to TRACE to analyze and troubleshoot the issue. |
| ISPN000546 |
Duplicate remote site '%s' in stack '%s' |
EXCEPTION |
The name for each cluster that participates in cross-site replication must have a
unique site name. Modify JGroups RELAY2 configuration and specify a unique site name
for each backup location. |
| ISPN000547 |
JGroups stack '%s' declares remote sites but does not include the RELAY2 protocol. |
EXCEPTION |
Cross-site replication requires the JGroups RELAY2 protocol. Modify the JGroups configuration
to include a RELAY2 stack. |
| ISPN000548 |
JGroups stack '%s' has a RELAY2 protocol without remote sites. |
EXCEPTION |
Each cluster that participates in cross-site replication must be identified with a
site name in the RELAY2 stack. Modify JGroups configuration and specify a unique site
name for each backup location. |
| ISPN000571 |
RELAY2 not found in the protocol stack. Cannot perform cross-site operations. |
EXCEPTION |
To back up caches from one site to another the cluster transport uses the JGroups
RELAY2 protocol. Add RELAY2 to your cluster transport configuration. |
| ISPN000576 |
Cross-site replication not available for local cache. |
EXCEPTION |
Cross-site replication capabilities do not apply to local cache mode. Either remove
the backup configuration from the local cache or use a distributed or replicated cache
mode. |
| ISPN000603 |
Cannot handle cross-site request from site '%s'. Cache '%s' not found. |
EXCEPTION |
A remote cluster attempted to replicate data to a cache that does not exist on the
local cluster. Either create the cache or modify the backup configuration for the
cache on the remote site. |
| ISPN000604 |
Cannot handle cross-site request from site '%s'. Cache '%s' is stopped. |
EXCEPTION |
A remote cluster attempted to replicate data to a cache that is not available. Start,
or restart, the cache. |
| ISPN000605 |
Cannot handle cross-site request from site '%s'. Cache '%s' is not clustered. |
EXCEPTION |
A remote cluster attempted to replicate data to a local cache. Either recreate the
cache with a distributed or replicated mode or remove the backup configuration. |
| ISPN000606 |
Remote site '%s' has an invalid cache configuration. Taking the backup location offline. |
ERROR |
An attempt was made to replicate data to a cache that does not have a valid configuration.
Check the cache at the remote site and recreate it with a valid distributed or replicated
configuration. |
| ISPN000607 |
The XSiteEntryMergePolicy is missing. The cache configuration must include a merge
policy. |
EXCEPTION |
To resolve conflicting entries between backup locations cache configuration must include
a merge policy. Recreate the cache and specify a merge policy from the org.infinispan.xsite.spi.XSiteMergePolicy
enum or use a conflict resolution algorithm. |
| ISPN000608 |
[IRAC] Unexpected error occurred. |
FATAL |
During conflict resolution for cross-site replication an unexpected error occurred.
To ensure data consistency between backup locations you should initiate state transfer
to synchronize data between clusters. |
| ISPN000617 |
Site '%s' not found. |
EXCEPTION |
A backup location that is configured as a site in the JGroups RELAY2 stack is not
available. Check the JGroups configuration and cache configuration to ensure that
the remote site is configured correctly. If the configuration is correct then check
that the backup location is online. |
| ISPN000618 |
Cleanup failed for cross-site state transfer. Invoke the cancel-push-state(%s) command
if any nodes indicate pending operations to push state. |
WARN |
When cross-site state transfer operations complete or fail due to a network timeout
or other exception, the coordinator node sends a cancel-push-state command to other
nodes. If any nodes indicate that there are pending operations to push state to a
remote site, you can invoke the cancel-push-state command again on those nodes. |
| ISPN000619 |
Cleanup failed for cross-site state transfer. Invoke the cancel-receive(%s) command
in site %s if any nodes indicate pending operations to receive state. |
WARN |
When cross-site state transfer operations complete or fail due to a network timeout
or other exception, the coordinator node sends a cancel-receive command to nodes.
If any nodes indicate that there are pending operations to receive state from a remote
site, you can invoke the cancel-receive command again. |
| ISPN000620 |
Cross-site state transfer to '%s' already started |
EXCEPTION |
An attempt was made to initiate cross-site state transfer while the operation was
already in progress. Wait for the state transfer operation to complete before initiating
a subsequent operation. Alternatively you can cancel the cross-site state transfer
operation that is in progress. |
| ISPN000633 |
Cross-site state transfer mode cannot be null. |
EXCEPTION |
The mode attribute for cross-site state transfer configuration must have a value of
AUTO or MANUAL. Modify the cache configuration with a valid value for the mode attribute. |
| ISPN000634 |
Cross-site automatic state transfer is not compatible with SYNC backup strategy. |
EXCEPTION |
Automatic state transfer is not possible if the backup strategy for cross-site replication
is synchronous. Modify the cache configuration and set the state transfer mode to
MANUAL. Alternatively you can change the backup strategy to use asynchronous mode. |
| ISPN000635 |
[%s] Failed to receive a response from any nodes. Automatic cross-site state transfer
to site '%s' is not started. |
WARN |
Before it starts automatic cross-site state transfer operations, the coordinator node
checks all local nodes to determine if state transfer is necessary. This error occurs
when the coordinator node gets an exception from one or more local nodes. Check that
nodes in the cluster are online and operating as expected. |
| ISPN000656 |
The backup '%s' configuration 'failure-policy=%s' is not valid with an ASYNC backup
strategy. |
EXCEPTION |
Only the 'WARN' and 'IGNORE' failure policies are compatible with asynchronous backups
for cross-site replication. Modify the backup configuration for the cache to change
the failure policy or use the synchronous backup strategy. |
| ISPN000657 |
The backup '%s' configuration 'failure-policy-class' is not compatible with 'failure-policy=%s'.
Use 'failure-policy="CUSTOM"' |
EXCEPTION |
The backup configuration for the cache specifies the fully qualified class of a custom
failure policy implementation. This is valid with the custom failure policy only.
Change the cache configuration to use 'failure-policy="CUSTOM"' or remove the failure
policy class. |
| ISPN000662 |
Failed to transfer cross-site tombstones to %s for segments %s. |
WARN |
Cross-site tombstones are metadata that ensure data consistency. This error indicates
that it was not possible to replicate tombstones for some segments during normal operations.
No action necessary. |