| commit | dd1b2817bbf7a0efce858414310a0c822ce89468 | [log] [tgz] |
|---|---|---|
| author | Nick Vatamaniuc <vatamane@apache.org> | Fri Jan 10 12:53:46 2020 -0500 |
| committer | Nick Vatamaniuc <nickva@users.noreply.github.com> | Fri Jan 10 14:58:05 2020 -0500 |
| tree | 9f68e1f92ccb6ea32ad7b8670e6dd7b17479d37f | |
| parent | 24201a34288b6d28c2153f6f9dc7f81bd50f8353 [diff] |
When shard splitting make sure to reset the targets before any retries Previously the target was reset only when the whole job started, but not when the initial copy phase restarted on its own. If that happened, we left the target around so the retry failed always with the `eexist` error. Target reset has a check to make sure the shards are not in the global shard map, in case someone manually added them, for example. If they are found there the job panics and exists.