Why does DRBD wait to be manually reconnected?

Eric Robinson <eric.robinson-JiDY2OCN/[email protected]>
Newsgroups gmane.comp.linux.drbd
Message-ID <SJ0PR03MB6501546AD11598630DF11E3CFA519@SJ0PR03MB6501.namprd03.prod.outlook.com>
Why does DRBD wait to be manually reconnected? For example...

[root@ha50a ~]# drbdadm status site586
site586 role:Secondary
  disk:UpToDate
  ha50b.mycharts.md role:Primary
    peer-disk:UpToDate
  quorum01 connection:StandAlone

[root@ha50a ~]# drbdadm connect site586:quorum01
[root@ha50a ~]# drbdadm status site586
site586 role:Secondary
  disk:UpToDate
  ha50b.mycharts.md role:Primary
    peer-disk:UpToDate
  quorum01 role:Secondary
    peer-disk:Diskless

Why doesn't DRBD try that itself?

Currently we have multiple resources in a Standalone state. To recover, I have to issue a connect command for each one. Shouldn't DRBD attempt that automatically?

[root@quorum01 ~]# lst r l|egrep -i "stand"
| site112      | ha51a-cl | 7275 | InUse  | StandAlone(quorum01)          |   UpToDate | 2022-04-05 10:05:56 |
| site187      | ha50a-cl | 7020 | InUse  | StandAlone(quorum01)          |   UpToDate | 2022-02-27 19:00:26 |
| site198      | ha52b-cl | 7432 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-06-02 23:24:02 |
| site206      | ha51a-cl | 7379 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-04-20 21:14:39 |
| site225      | ha50a-cl | 7179 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-03-22 23:07:03 |
| site312      | ha51b-cl | 7265 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-04-05 00:02:58 |
| site357      | ha51a-cl | 7336 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-04-12 21:11:10 |
| site367      | ha51b-cl | 7272 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-04-05 01:26:59 |
| site458      | ha51b-cl | 7196 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-03-25 00:32:07 |
| site496      | ha51a-cl | 7295 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-04-07 15:36:33 |
| site530      | ha50b-cl | 7018 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-02-27 18:11:33 |
| site586      | ha50a-cl | 7130 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-03-18 18:31:51 |
| site734      | ha50a-cl | 7119 | Unused | StandAlone(quorum01)          |   UpToDate | 2022-03-17 17:47:00 |
| site744      | ha51b-cl | 7411 | InUse  | StandAlone(quorum01)          |   UpToDate | 2022-04-26 18:29:07 |

[cid:image001.png-fcDHA2R9KojrK2/[email protected]]

Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
[email protected]
https://lists.linbit.com/mailman/listinfo/drbd-user
image001.png (image/png, 151.9 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.