On Fri, Mar 15, 2019 at 9:24 PM Taste-Of-IT wrote:
> Hi,
>
> ok this seems to be a bug. I now update from 3.x to 4.x to 5.x Latest
> Debian Releases. After each Upgrade i run remove-brick and the problem is
> still the same. Gluster ignores storage.reserve Option. Positiv is that the
>
Hi,
i am trying to understand why georeplciation during "History Crawl" starts
failing on each of the three bricks, one after the other. I have enabled
DEBUG for all the logs configurable by the geo-replication command.
Running glusterfs v4.16 the behaviour is as follow:
- The "History Crawl"
