IMO, this is a intended behavior. Object expirer's job is fixing this mismatching. So, fundamentally, a solution can be running object expirer often. :(
If we can assume that object expirer should be expired(because of this kinds of phantom objects), and we should put the expiring jobs on suitable places in obj/server.py & changing the DB schema of container, and so on. But I think, this discussion went beyond this bug. It should be blueprints or other discussions. IMHO, viable solution for this bug right now is that notifying of expiration to container when expired object is requested as GET/HEAD. this can avoid the reported scenario with few overhead(requesting expired objects looks rare). -- 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
