MDC replicated objects are missing HTTP headers after upgrading from 1.3.0 to 1.3.2.1

[Peter Toth]

Hi all,

After upgrading to 1.3.2.1 both of our multi DC clusters (in total 4 independent clusters) are experiencing the same issue.

I have raised this issue at https://github.com/leo-project/leofs/issues/641

Both clusters are set up with MDC replication.

In a nutshell, once a file is replicated from DC "A" to the remote DC "B" it is not possible to retrieve the file from the bucket with s3cmd (will result in an s3cmd error).

Pulling the file out with curl works but completely missing all HTTP headers and truncated by 3 bytes.

This is 100% reproducible on both of our MDC clusters.

Regards,

Peter

[yoshiyuki kanno]

For those who don't track the issues on github.

This issue filed on github https://github.com/leo-project/leofs/issues/641 .
It turned out that the custom metadata support
https://github.com/leo-project/leofs/issues/107 introduced in 1.3.1
cause this regression when MDC enabled.
The detail is available on the above issue.

Best,
Kanno.

> --
> You received this message because you are subscribed to the Google Groups
> "LeoProject.LeoFS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to leoproject_leo...@googlegroups.com.
> To post to this group, send email to leoproje...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/leoproject_leofs/9a8181ab-2159-4830-ad9a-8f67aee70f56%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Yoshiyuki Kanno
LeoFS Committer(http://www.leofs.org)
--------------------------------------------------
Stoic Corp.
URL: http://www.stoic.co.jp/
E-mail: yoshiyu...@stoic.co.jp