|
32 | 32 | <itemizedlist> |
33 | 33 | <listitem> |
34 | 34 | <para> |
35 | | - In two-node clusters, you can now set up a major node that |
36 | | - continues working even if there is no quorum. |
37 | | - For details, see <xref linkend="configuring-the-major-node">. |
38 | | - </para> |
39 | | - </listitem> |
40 | | - <listitem> |
41 | | - <para> |
42 | | - Using a separate <application>referee</application> extension, |
| 35 | + Added a new extension (<application>referee</application>) |
| 36 | + for managing quorum settings. With this extension, |
43 | 37 | you can set up a standalone referee node for your cluster to |
44 | 38 | assign the quorum status to a subset of nodes that constitutes |
45 | 39 | half of the cluster. |
46 | 40 | For details, see <xref linkend="setting-up-a-referee">. |
47 | 41 | </para> |
48 | 42 | </listitem> |
| 43 | + <listitem> |
| 44 | + <para> |
| 45 | + Added a new parameter for choosing a major node in two-node |
| 46 | + clusters. You can now set up a major node that |
| 47 | + continues working even if there is no quorum. |
| 48 | + For details, see <xref linkend="configuring-the-major-node">. |
| 49 | + </para> |
| 50 | + </listitem> |
49 | 51 | </itemizedlist> |
50 | 52 | </para> |
51 | 53 | </listitem> |
|
