Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
the link between nodes is ??? 1Gb/s ??? , 10Gb/s ??? ...
the Hard Disks are ??? SATA 7200rpm ???, 10000rpm ???, SAS ???,
SSD ???...
400M to 680M with a 10Gb/s link and SAS 15.000 rpm is OK but less ...
El dom, 24-05-2015 a las 20:43 +0200, Ben RUBSON escribió:
> > Le 12 avr. 2014 à 17:23, Ben RUBSON <ben.rubson at gmail.com> a écrit :
> >
> > Hello,
> >
> > Let's assume the following configuration :
> > disk {
> > c-plan-ahead 0;
> > resync-rate 680M;
> > c-min-rate 400M;
> > }
> >
> > Both nodes are uptodate, and on the primary, I have a test IO burst running, using dd.
> >
> > I then cut replication link for a few minutes so that secondary node will be several GB behind primary node.
> >
> > I then re-enable replication link.
> > What I expect here according to the configuration is that secondary node will fetch missing GB at a 400 MB/s throughput.
> > DRBD should then prefer resync IOs over application (dd here) IOs.
> >
> > However, it does not seems to work.
> > dd still writes at its best throughput, meanwhile reads are made from the primary disk between 30 and 60 MB/s to complete the resync.
> > Of course this is not the expected behaviour.
> >
> > Did I miss something ?
>
> Hello,
>
> Could I have your feedback please regarding this ?
>
> Thank you !
>
> Ben
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user