Project

General

Profile

Task #3465

Improve Metacat listObject slicing

Added by Ben Leinfelder over 8 years ago. Updated over 8 years ago.

Status:
New
Priority:
Normal
Assignee:
Ben Leinfelder
Category:
Metacat
Target version:
-
Start date:
2012-12-07
Due date:
% Done:

0%

Milestone:
CCI-1.1.1
Product Version:
*
Story Points:
Sprint:

Description

Story for organizing MN and CN listObject slicing. We have done all we can for the CN given our current architecture (3+ CN responding to requests somewhat randomly).
We should add a synthetic key for Metacat's systemMetadata table and order by that key (not guid). This will ensure consistent slicing for the MN implementation of listObjects since there is only ever a single server in the mix.
Please also see the related bugs that give more background to this story.


Subtasks

Task #3466: Add synthetic key to systemMetadata tableNewBen Leinfelder

Task #3467: MN.listObject should use auto-incremented keyNewBen Leinfelder

Task #3468: Explore how CN.listObject can effectively use auto-incremented keyNewBen Leinfelder

Task #3414: Add sequence id to systemMetadata table for slicingRejectedBen Leinfelder


Related issues

Related to Infrastructure - Bug #3065: cn.listObjects slicing broken in production Closed 2012-12-02 2013-01-05
Related to Infrastructure - Bug #3128: Production CN listObjects slow response Closed 2012-08-13 2013-01-05

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)