[Bug 1069849] Re: Containers show expired objects
Unfortunately, a simple deletion of objects isn't so simple. If a container has millions of expired-but-not-deleted objects in it, then it'll take millions of deletions to delete the container. That can't be the proxy's responsibility; it'll take a really long time to do all those deletions, and the proxy has to return a response to the client in a reasonable amount of time. Also, even listing the container's objects to determine if they're all expired can be expensive. A container with 1 million expired objects and 1 single non-expired object isn't eligible for deletion; to even list all those objects (at 10,000 entries per listing request) would take 102 requests to container servers. So, clearly we can't do this in response to a request. Perhaps the answer is to move expired-object deletion into a different process, like the object-auditor or object-replicator. That way there's not a SPOF like there is with the object-expirer. In that case, you'd still have a window to see expired-but-not-deleted objects, but you could delete them yourself if necessary. However, the failure of a single process wouldn't cause expired-object deletion to halt. I haven't had time to think through all the tradeoffs, though, so that may actually be a bad idea. Not sure yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069849] Re: Containers show expired objects
Swift's response to a DELETE of an expired object is 404; however, the object does get deleted. Thus, you can clean out the expired-but- undeleted objects from a container and then delete the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069849] Re: Containers show expired objects
Actually, this raises an interesting point. Without this bugfix, a container listing shows expired objects, enabling users to delete their containers even if the object expirer is running slowly (after deleting their expired objects, of course). With a fix for this bug, users would be saddled with empty-looking, undeletable containers. Perhaps we should choose not to fix this bug, as the fix may add more problems than it removes. Thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 961640] Re: Swift-Bench Error3 on Ubuntu Precise
There have been a lot of changes to swift-bench since version 1.4.7. Is this still a problem? ** Changed in: swift Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/961640 Title: Swift-Bench Error3 on Ubuntu Precise To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/961640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070288] Re: x-object-manifest does not work with quoted names
The bug could be in one of two places: either (a) in python-swiftclient, or (b) in Swift. If you perform these operations using curl or some other plain-HTTP client, does the bug occur, or does it only happen when using python-swiftclient? ** Changed in: swift Status: New = Incomplete ** Changed in: python-swiftclient Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070288 Title: x-object-manifest does not work with quoted names To manage notifications about this bug go to: https://bugs.launchpad.net/python-swiftclient/+bug/1070288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069849] Re: Containers show expired objects
To fix this, Swift would have to store object expiration times in the container DB. That's not currently in the schema, so there'd have to be migration code added. Also, the object server would have to send an update to the container server when there's a change in the value of X-Delete-At. It's not a trivial change. ** Changed in: swift Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069849 Title: Containers show expired objects To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1069849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
