Chris Lu

same issue as fixed in https://github.com/seaweedfs/seaweedfs/pull/5820 ?

https://github.com/seaweedfs/seaweedfs/pull/5820 is not released yet.

can you try `-target node-x.d.example.com:30015.30025` see https://github.com/seaweedfs/seaweedfs/wiki/FAQ#grpc-ports

The `volume.tier.upload` is calling this function https://github.com/seaweedfs/seaweedfs/blob/master/weed/shell/command_volume_tier_upload.go#L84 defined in https://github.com/seaweedfs/seaweedfs/blob/master/weed/shell/command_ec_encode.go#L290 Could not eyeball to find the bug. Could you do some println debugging to see what went wrong?

No Azure account to test it this. Mostly the bug is around https://github.com/seaweedfs/seaweedfs/blob/master/weed/replication/sink/azuresink/azure_sink.go#L119

you may change ParityShardsCount to 5 here: https://github.com/seaweedfs/seaweedfs/blob/master/weed/storage/erasure_coding/ec_encoder.go#L19 So it would be 10+5.

it's a bit complicated. If making it configurable, it would affect many components.

no good clue

Sorry to reply late. This filer-layer requirement caused changes on the block storage layer about TTL and garbage collection. There are other possible implications on data racing, replication, etc. Besides,...

* Even when the volume last modified time is updated, the TTL volume may still be compacted and the entry can still be dropped. * It's simpler to just create...