#289 ✓closed
Paul Jones

Failed scans aren't cancelling internally

Reported by Paul Jones | 2011-07-13 09:24:27 UTC

When one leg of a scan fails, the scan isn't being marked as failed. This then means that the other leg will continue on, and usually doesn't stop until it either completes or it attempts to write. If it does attempt to write, then it will receive a timeout from the VersionCorrelationWriterProxy, since the main receive loop logs and error and fails to respond if it gets a VersionCorrelationWriterCommand.

To make scans fail more cleanly, we should:

  • Cancel the current feedback handle when either of the legs fails;
  • Change the VersionCorrelationWriterProxy response message to be either Correlation or Cancelled, and generate a ScanCancelledException if the Cancelled message is returned.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

A Real Time Differencing Tool.

Shared Ticket Bins

People watching this ticket

Pages