Thanks, John. I am happy to try out Swift EC and will report bugs to launchpad if necessary.
(The issue I found happens to be different from the ones listed in the bug list. See my other email) Thanks Changbin On Tue, Jul 21, 2015 at 5:05 PM, John Dickinson <[email protected]> wrote: > Yes, it's supposed to work, but you've run in to some errors we've been > finding and fixing. Right now the top priority for the Swift dev community > is to take care of the outstanding EC issues and make a release. > > The list of the known EC bugs right now is > https://bugs.launchpad.net/swift/+bugs?field.tag=ec. You'll see that > nearly all of them are handled, and the rest are being worked on. We will > have them fixed and a new Swift release ASAP. > > Specifically, I think you were hitting bug > https://bugs.launchpad.net/swift/+bug/1469094 (or maybe > https://bugs.launchpad.net/swift/+bug/1452619). > > I'm so happy you're trying out erasure codes in Swift! That's exactly what > we need to happen. As the docs say, it's still a "beta" feature. Please let > us know what you find. Bug reports are very helpful, but even mailing list > posts or dropping in the #openstack-swift channel in IRC is appreciated. > > --John > > > > > > On Jul 21, 2015, at 1:38 PM, Changbin Liu <[email protected]> > wrote: > > > > Folks, > > > > To test the latest feature of Swift erasure coding, I followed this > document ( > http://docs.openstack.org/developer/swift/overview_erasure_code.html) to > deploy a simple cluster. I used Swift 2.3.0. > > > > I am glad that operations like object PUT/GET/DELETE worked fine. I can > see that objects were correctly encoded/uploaded and downloaded at proxy > and object servers. > > > > However, I noticed that swift-object-reconstructor seemed don't work as > expected. Here is my setup: my cluster has three object servers, and I use > this policy: > > > > [storage-policy:1] > > policy_type = erasure_coding > > name = jerasure-rs-vand-2-1 > > ec_type = jerasure_rs_vand > > ec_num_data_fragments = 2 > > ec_num_parity_fragments = 1 > > ec_object_segment_size = 1048576 > > > > After I uploaded one object, I verified that: there was one data > fragment on each of two object servers, and one parity fragment on the > third object server. However, when I deleted one data fragment, no matter > how long I waited, it never got repaired, i.e., the deleted data fragment > was never regenerated by the swift-object-reconstructor process. > > > > My question: is swift-object-reconstructor supposed to be "NOT WORKING" > given the current implementation status? Or, is there any configuration I > missed in setting up swift-object-reconstructor? > > > > Thanks > > > > Changbin > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > [email protected]?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
