normalocity/keyspace — Issue #70: Move the receiving of a backup job into its own Job
Author: normalocity
Created: 2011-10-12 12:28:37+00:00
State: open
Labels: Bug

This is necessary in order to keep the KeySetGeneratorBackupService from appearing to hang on a backup request that is invalid, or from the incorrect group.

Currently, if a peer backup request comes in, the KeySetGeneratorBackupService picks up the request, and tries to read the data. If there is any kind of delay in receiving the data, or if the connection is made by no backup is actually sent, the result will be that the KeySetGeneratorBackupService will sit idle for at least as long as the socket timeout.

While this is problematic on its own, it could also be used deliberately to prevent the service from doing its basic job, essentially breaking peer backups for an indefinite amount of time.