<p><b><big>Model</big></b><br>Specifies the model to be used. This parameter is required.corosync-qdevice is modular and is able to support multiple different models. The model basically defines what type of arbitrator is used. Currently only 'net' is supported.</p> <p><b><big>Host</big></b><br>Specifies the IP address or host name of the qnetd server to be used. This parameter is required.</p> <p><b><big>Port</big></b><br>Specifies TCP port of qnetd server. Default is 5403.</p> <p><b><big>TLS</big></b><br>Can be one of 'on', 'off' or 'required' and specifies if tls should be used. 'on' means a connection with TLS is attempted first, but if the server doesn't advertise TLS support then non-TLS will be used. 'off' is used then TLS is not required and it's then not even tried. This mode is the only one which doesn't need a properly initialized NSS database. 'required' means TLS is required and if the server doesn't support TLS, qdevice will exit with error message. 'on' need manually change, refer to corosync-qdevice's man page for more details. Default is 'off' in yast.</p> <p><b><big>Algorithm</big></b><br>Decision algorithm. Can be one of the 'ffsplit' or 'lms'.(Actually there are also 'test' and '2nodelms', both of which are mainly for developers and shouldn't be used for production clusters, so yast will convert to 'ffsplit' automatically). For a description of what each algorithm means and how the algorithms differ see their individual sections.Default value is ffsplit.</p> <p><b><big>Tie breaker</big></b><br>Can be one of 'lowest', 'highest' or 'valid_node_id' (number) values. It's used as a fallback if qdevice has to decide between two or more equal partitions. 'lowest' means the partition with the lowest node id is chosen. 'highest' means the partition with highest node id is chosen. And 'valid_node_id' means that the partition containing the node with the given node id is chosen. Default is 'lowest'.</p> <p><b><big>Qdevice Heuristics</big></b><br>Subsection of Qdevice. Heuristics are set of commands executed locally on startup, cluster membership change, successful connect to corosync-qnetd and optionally also at regular times. Commands are executed in parallel. When *all* commands finish successfully (their return error code is zero) on time, heuristics have passed, otherwise they have failed. The heuristics result is sent to corosync-qnetd and there it's used in calculations to determine which partition should be quorate.</p> <p><b><big>Heuristics Mode</big></b><br>Can be one of on, sync or off and specifies mode of operation of heuristics. Default is off, whichmeansheuristics are disabled. When sync is set, heuristics are executed only during startup, membership change and when connection to corosync-qnetd is established. When heuristics should be running also on regular basis, this option should be set to on value.</p> <p><b><big>Heuristics Timeout</big></b><br>Specifies maximum time in milliseconds. How long corosync-qdevice waits till the heuristics commands finish. If some command doesn't finish before the timeout, it's killed and heuristics fail. This timeout is used for heuristics executed at regular times. Default value is half of the quorum.device.timeout, so 5000.</p> <p><b><big>Heuristics Sync_timeout</big></b><br>Similar to quorum.device.heuristics.timeout but used during membership changes. Default value is half of the quorum.device.sync_timeout, so 15000.</p> <p><b><big>Heuristics Interval</big></b><br>Specifies interval between two regular heuristics execution. Default value is 3 * quorum.device.timeout, so 30000.</p> <p><b><big>Heuristics exec_NAME</big></b><br>Defines executables. *NAME* can be arbitrary valid cmap key name string and it has no special meaning. The value of this variable must contain a command to execute. The value is parsed (split) into arguments similarly as Bourne shell would do. Quoting is possible by using backslash and double quotes. <br>For example, Name(exec_check_master), Value(/etc/corosync/qdevice/check_master.sh)</p>
<p> <b><big>Model</big></b> <br> Menentukan model yang akan digunakan. Parameter ini wajib diisi. corosync-qdevice bersifat modular dan mampu mendukung beberapa model berbeda. Model tersebut pada dasarnya menentukan jenis arbitrator yang digunakan. Saat ini hanya 'net' yang didukung. </p><p> <b><big>Tuan rumah</big></b> <br> Menentukan alamat IP atau nama host dari server qnetd yang akan digunakan. Parameter ini wajib diisi. </p><p> <b><big>Pelabuhan</big></b> <br> Menentukan port TCP dari server qnetd. Default-nya adalah 5403. </p><p> <b><big>TLS</big></b> <br> Bisa salah satu dari 'on', 'off' atau 'required' dan menentukan apakah tls harus digunakan. 'on' berarti koneksi dengan TLS dicoba terlebih dahulu, tetapi jika server tidak mengiklankan dukungan TLS maka non-TLS akan digunakan. 'off' digunakan maka TLS tidak diperlukan dan bahkan tidak dicoba. Mode ini adalah satu-satunya yang tidak memerlukan database NSS yang diinisialisasi dengan benar. 'diperlukan' berarti TLS diperlukan dan jika server tidak mendukung TLS, qdevice akan keluar dengan pesan kesalahan. 'on' perlu diubah secara manual, lihat halaman manual corosync-qdevice untuk lebih jelasnya. Default-nya adalah 'off' di yast. </p><p> <b><big>Algoritma</big></b> <br> Algoritma keputusan. Bisa salah satu dari 'ffsplit' atau 'lms'. (Sebenarnya ada juga 'test' dan '2nodelms', keduanya terutama untuk developer dan tidak boleh digunakan untuk cluster produksi, jadi yast akan mengonversi menjadi 'ffsplit' secara otomatis). Untuk penjelasan tentang arti setiap algoritme dan bagaimana algoritme berbeda, lihat bagian masing-masing. Nilai defaultnya adalah ffsplit. </p><p> <b><big>Pemecah dasi</big></b> <br> Bisa salah satu dari nilai 'terendah', 'tertinggi' atau 'valid_node_id' (angka). Ini digunakan sebagai fallback jika qdevice harus memutuskan antara dua atau lebih partisi yang sama. 'terendah' berarti partisi dengan id node terendah dipilih. 'tertinggi' berarti partisi dengan id node tertinggi dipilih. Dan 'valid_node_id' berarti partisi yang berisi node dengan id node yang diberikan dipilih. Default-nya adalah 'terendah'. </p><p> <b><big>Qdevice Heuristics</big></b> <br> Subbagian dari Qdevice. Heuristik adalah sekumpulan perintah yang dijalankan secara lokal saat startup, perubahan keanggotaan cluster, berhasil terhubung ke corosync-qnetd dan secara opsional juga pada waktu reguler. Perintah dijalankan secara paralel. Ketika * semua * perintah selesai dengan sukses (kode kesalahan yang dikembalikan adalah nol) tepat waktu, heuristik telah berlalu, jika tidak maka gagal. Hasil heuristik dikirim ke corosync-qnetd dan digunakan dalam kalkulasi untuk menentukan partisi mana yang harus quorate. </p><p> <b><big>Mode Heuristik</big></b> <br> Bisa salah satu aktif, sinkronkan atau nonaktifkan dan menentukan mode operasi heuristik. Default tidak aktif, yang berarti heuristik dinonaktifkan. Saat sinkronisasi disetel, heuristik dijalankan hanya selama penyalaan, perubahan keanggotaan, dan saat sambungan ke corosync-qnetd dibuat. Jika heuristik harus dijalankan juga secara teratur, opsi ini harus disetel ke nilai. </p><p> <b><big>Batas Waktu Heuristik</big></b> <br> Menentukan waktu maksimum dalam milidetik. Berapa lama corosync-qdevice menunggu hingga perintah heuristik selesai. Jika beberapa perintah tidak selesai sebelum batas waktu, perintah tersebut dihentikan dan heuristik gagal. Batas waktu ini digunakan untuk heuristik yang dijalankan pada waktu biasa. Nilai defaultnya adalah setengah dari quorum.device.timeout, jadi 5000. </p><p> <b><big>Heuristics Sync_timeout</big></b> <br> Mirip dengan quorum.device.heuristics.timeout tetapi digunakan selama perubahan keanggotaan. Nilai default-nya adalah setengah dari quorum.device.sync_timeout, jadi 15000. </p><p> <b><big>Interval Heuristik</big></b> <br> Menentukan interval antara dua eksekusi heuristik reguler. Nilai defaultnya adalah 3 * quorum.device.timeout, jadi 30000. </p><p> <b><big>Eksekutif heuristik</big></b> <br> Mendefinisikan executable. * NAME * dapat berupa string nama kunci cmap yang valid dan tidak memiliki arti khusus. Nilai variabel ini harus berisi perintah untuk dieksekusi. Nilai diuraikan (dibagi) menjadi argumen yang sama seperti yang akan dilakukan oleh shell Bourne. Mengutip dimungkinkan dengan menggunakan garis miring terbalik dan tanda kutip ganda. <br> Misalnya, Nama (exec_check_master), Nilai (/etc/corosync/qdevice/check_master.sh) </p>
<p><b><big>Host</big></b><br>Specifies the IP address or host name of the qnetd server to be used. This parameter is required.</p>
<p><b><big>Port</big></b><br>Specifies TCP port of qnetd server. Default is 5403.</p>
<p><b><big>TLS</big></b><br>Can be one of 'on', 'off' or 'required' and specifies if tls should be used. 'on' means a connection with TLS is attempted first, but if the server doesn't advertise TLS support then non-TLS will be used. 'off' is used then TLS is not required and it's then not even tried. This mode is the only one which doesn't need a properly initialized NSS database. 'required' means TLS is required and if the server doesn't support TLS, qdevice will exit with error message. 'on' need manually change, refer to corosync-qdevice's man page for more details. Default is 'off' in yast.</p>
<p><b><big>Algorithm</big></b><br>Decision algorithm. Can be one of the 'ffsplit' or 'lms'. (Actually there are also 'test' and '2nodelms', both of which are mainly for developers and shouldn't be used for production clusters, so yast will convert to 'ffsplit' automatically). For a description of what each algorithm means and how the algorithms differ see their individual sections. Default value is ffsplit.</p>
<p><b><big>Tie breaker</big></b><br>Can be one of 'lowest', 'highest' or 'valid_node_id' (number) values. It's used as a fallback if qdevice has to decide between two or more equal partitions. 'lowest' means the partition with the lowest node id is chosen. 'highest' means the partition with highest node id is chosen. And 'valid_node_id' means that the partition containing the node with the given node id is chosen. Default is 'lowest'.</p>
<p><b><big>Qdevice Heuristics</big></b><br>Subsection of Qdevice. Heuristics are set of commands executed locally on startup, cluster membership change, successful connect to corosync-qnetd and optionally also at regular times. Commands are executed in parallel. When *all* commands finish successfully (their return error code is zero) on time, heuristics have passed, otherwise they have failed. The heuristics result is sent to corosync-qnetd and there it's used in calculations to determine which partition should be quorate.</p>
<p><b><big>Heuristics Mode</big></b><br>Can be one of on, sync or off and specifies mode of operation of heuristics. Default is off, which means heuristics are disabled. When sync is set, heuristics are executed only during startup, membership change and when connection to corosync-qnetd is established. When heuristics should be running also on regular basis, this option should be set to on value.</p>
<p><b><big>Heuristics Timeout</big></b><br>Specifies maximum time in milliseconds. How long corosync-qdevice waits till the heuristics commands finish. If some command doesn't finish before the timeout, it's killed and heuristics fail. This timeout is used for heuristics executed at regular times. Default value is half of the quorum.device.timeout, so 5000.</p>
<p><b><big>Heuristics Sync_timeout</big></b><br>Similar to quorum.device.heuristics.timeout but used during membership changes. Default value is half of the quorum.device.sync_timeout, so 15000.</p>
<p><b><big>Heuristics Interval</big></b><br>Specifies interval between two regular heuristics execution. Default value is 3 * quorum.device.timeout, so 30000.</p>
<p><b><big>Heuristics exec_NAME</big></b><br>Defines executables. *NAME* can be arbitrary valid cmap key name string and it has no special meaning. The value of this variable must contain a command to execute. The value is parsed (split) into arguments similarly as Bourne shell would do. Quoting is possible by using backslash and double quotes. <br>For example, Name(exec_check_master), Value(/etc/corosync/qdevice/check_master.sh)</p>