https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2013-04-02T16:04:05ZDataONE TasksInfrastructure - Bug #3700: MNodeService.replicate will not request new object if existing on MNhttps://redmine.dataone.org/issues/3700?journal_id=158272013-04-02T16:04:05ZSkye Roseboomsroseboo@dataone.unm.edu
<ul></ul><p>I think this is a low priority issue at the moment. Current strategy in ReplicationManager will avoid attempting to place a new replica copy on a MN with an invalid copy of the object. Might become more of an issue in the future.</p>
<p>However, this may be a policy issue for member node implementations - as to what the expectations of the replicate service are when the object is already on the member node (but with invalid checksum or maybe actually NotFound).</p>
Infrastructure - Bug #3700: MNodeService.replicate will not request new object if existing on MNhttps://redmine.dataone.org/issues/3700?journal_id=221022014-10-01T21:55:00ZDave Vieglaisdave.vieglais@gmail.com
<ul><li><strong>Due date</strong> set to <i>2014-12-01</i></li><li><strong>Target version</strong> set to <i>CCI-2.0.0</i></li><li><strong>Start date</strong> set to <i>2014-12-01</i></li></ul> Infrastructure - Bug #3700: MNodeService.replicate will not request new object if existing on MNhttps://redmine.dataone.org/issues/3700?journal_id=233512015-01-06T19:43:15ZSkye Roseboomsroseboo@dataone.unm.edu
<ul><li><strong>Due date</strong> changed from <i>2014-12-01</i> to <i>2015-01-06</i></li><li><strong>Target version</strong> changed from <i>CCI-2.0.0</i> to <i>Release Backlog</i></li></ul>