General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Updated Category
8856InfrastructureStoryNewNormalPut the system metadata part ahead of the object part when d1_client_python constructs the multipart2019-11-22 18:31d1_python
4463InfrastructureStoryIn ProgressNormalIncorporate Node Replication Policy into replication processingRob Nahf2018-01-17 20:03d1_replication
8641InfrastructureBugNewNormalAny change to SystemMetadata causes a new replication task to be generated without consideration of the object replicabilityChris Jones2018-07-04 12:28d1_replication
7178InfrastructureBugNewNormalduplicate replica information on mn-demo-5Robert Waltz2015-07-01 20:14d1_replication
8162InfrastructureStoryNewNormalReplication tasks can contain stale potential target nodesRob Nahf2018-03-02 21:47d1_replication
8640InfrastructureBugNewNormalReplication includes "down" nodes as replication targetsChris Jones2018-07-04 11:29d1_replication
2585InfrastructureTaskIn ProgressNormalUpdate Use Case 09Skye Roseboom2014-09-11 15:47d1_replication
8196InfrastructureBugNewNormalDuplicated replicas in the system metadataJing Tao2017-10-18 17:19d1_replication
6377InfrastructureStoryIn ProgressNormalReview CNode initialization in ReplicationManager - it doesn't use local CN referenceRob Nahf2018-01-17 19:52d1_replication
6372InfrastructureTaskIn ProgressNormalrehabilitate ReplicationManager "unit" testsRob Nahf2016-06-22 16:53d1_replication
6378InfrastructureTaskTestingNormalcode up the new strategyRob Nahf2016-06-22 16:53d1_replication
4038InfrastructureFeatureNewNormalchange default replication implementationMatthew Jones2014-10-01 21:26d1_replication
8642InfrastructureBugNewNormalReplication tasks apparently not deleted from backing store in a timely fashionDave Vieglais2018-07-05 12:11d1_replication
6376InfrastructureTaskNewNormaltest the new strategy against working ReplicationManager testRob Nahf2016-06-22 16:53d1_replication
6375InfrastructureTaskIn ProgressNormalRefactor out dependency on a working CNRob Nahf2016-06-22 16:53d1_replication
8639InfrastructureStoryNewNormalReplication performance is too slow to service demandChris Jones2018-07-04 11:18d1_replication
8108InfrastructureSupportNewNormalMust determine the state of replication auditing for when replicas on non-functioning MNs are still reported as completeDave Vieglais2017-06-06 17:56d1_replication_auditor
4189InfrastructureTaskIn ProgressNormalUpdate dataoneErrors.xsd to match the documentationDave Vieglais2017-01-14 00:24d1_schemas
2827InfrastructureTaskIn ProgressNormalnesting groups requires schema change*Dave Vieglais2015-06-25 22:00d1_schemas
4188InfrastructureStoryIn ProgressNormaldataone Exception definition and implementation requires clarificationDave Vieglais2018-01-17 20:05d1_schemas
8038InfrastructureStoryIn ProgressNormalconnect logging output to a log analysis toolDave Vieglais2018-01-17 18:52d1_synchronization
8573InfrastructureBugIn ProgressNormalchanging accessPolicies and rightHolders down the line of series can cause improper sync failuresRob Nahf2018-05-03 21:52d1_synchronization
7889InfrastructureStoryNewNormalSynchronization not happening when authoritativeMN is not set correctly.Rob Nahf2018-01-17 19:01d1_synchronization
8106InfrastructureBugTestingNormalDifficulty Distinguishing Between Different Kinds of Failed Sync "Not Found" Error MessagesRob Nahf2018-02-20 16:57d1_synchronization
2488InfrastructureStoryNewNormalChanging the authoritativeMembernode will require all replica's systemMetadata be updatedDave Vieglais2018-01-17 20:39d1_synchronization
(251-275/1153) Per page: 25, 50, 100, 500

Also available in: Atom CSV PDF

Add picture from clipboard (Maximum size: 14.8 MB)