Skip to content

erp5
erp5
Commit a2606bc7 authored by Vincent Pelletier's avatar Vincent Pelletier
Browse files
Options

Store existing nodes as a BTree: 

 - limits conflict errors (the list is automaticaly modified, though rarely)
 - allows to store key, value pairs
Cache processingNode computation result.
Add accessors to node btree.
Remove manage_addNode as it's now automaticaly done.
Update iser interface and add new required methods.
Automaticaly register self as an available processing node when process_timer is called.
Use distributing node accessor instead of accessing the value directly.
Empty processing node list and no defined distributing node means now that the feature is disabled, not that every node distributes and process.
Display the ip:port value which identifies current node on the user interface.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@16940 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent 098eeed3
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 208 additions and 149 deletions
product/CMFActivity/ActivityTool.py
View file @ a2606bc7
This diff is collapsed.
product/CMFActivity/dtml/manageLoadBalancing.dtml
View file @ a2606bc7
......@@ -44,130 +44,137 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
Zope Configuration File <i>zope.conf</i>.
</p>
<p class="form-help">
The <i>Distributing node</i> is responsible for the Load Distribution. The default value is empty
which means that every existing node will try to do the distribution, which is fine when there
is only one ZServer running.
To change the Distributing Node, edit the value and click &quot;Change&quot;.
</p>
<form action="&dtml-URL1;">
<table cellspacing="0" cellpadding="2" border="0" width="100%">
<tr class="list-header">
<td align="left" valign="top" colspan=2>
<div class="form-label">Distributing Node</div>
<div class="form-label">This node</div>
</td>
</tr>
<tr>
<td>
<div class="form-label">IP:Port</div>
</td>
<td align="left">
<div class="form-item">
<input type="text" name="distributingNode" value="&dtml-getDistributingNode;" size="19" />
</div>
</td>
</tr>
<tr>
<td>&nbsp;</td>
<td align="left">
<div class="form-element">
<input type="submit" class="form-element" name="manage_setDistributingNode:method" value=" Change ">
</div>
</td>
<td colspan=2>Current node is <b><dtml-var getCurrentNode></b></td>
</tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td align="left" colspan=2>
<p class="form-help">
The following list defines the nodes the Load is currently distributed to. Per default this list is empty
which means that every existing node will try to process all activities, which is fine, when ther is only one
ZServer running.
To delete a node from the list, activate the checkbox on the left of that node and click the &quot;Delete&quot; button.
</p>
</td>
</tr>
<tr class="list-header">
<td align="left" valign="top" colspan=2>
<div class="form-label">Existing Nodes</div>
</td>
<dtml-in getNodes>
<dtml-let domain=sequence-key
node=sequence-item
index=sequence-index>
<tr class="row-normal">
<td align="left" valign="top">
<input type="checkbox" name="deleteNodes:list" value="&dtml-node;">
</td>
<td align="left" valign="top">
<dtml-if "domain == _.None">
<p>Default</p>
<dtml-else>
<p><dtml-var node></p>
</dtml-if>
<div class="form-label">Distributing Node</div>
</td>
</tr>
</dtml-let>
</dtml-in>
<tr>
<td align="left" colspan="2">
<div class="form-element">
<input type="submit" class="form-element" name="manage_delNode:method" value=" Delete " />
</div>
<td>
<select name="distributingNode">
<option value="">(disabled)</option>
<dtml-in getNodeList prefix="node">
<dtml-if expr="node_item == getDistributingNode()">
<option selected="selected" value="<dtml-var sequence-item>">
<dtml-var sequence-item>
</option>
<dtml-else>
<option value="<dtml-var sequence-item>">
<dtml-var sequence-item>
</option>
</dtml-if>
</dtml-in>
</select>
<input type="submit" class="form-element" name="manage_setDistributingNode:method" value=" Change ">
</td>
<td>
<p class="form-help">
The <i>Distributing node</i> is responsible for the Load Distribution.
Only one node can be <i>Distributing node</i> at any given time.
It is also possible to interupt activity distribution by selecting the
<i>(disabled)</i> value. Activity nodes will receive no more activity
when <i>Distributing node</i> is disabled.
</p>
</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<tr class="list-header">
<td align="left" valign="top" colspan=2>
<p class="form-help">
To add a new node, enter the Ip-Address and Port-Number for the new node
and click the &quot;Add&quot; button.
</p>
<div class="form-label">Existing Nodes</div>
</td>
</tr>
<tr>
<td>
<div class="form-label">IP:Port</div>
</td>
<td align="left">
<div class="form-item"><input type="text" name="node" size="19" /></div>
<table>
<tr>
<td rowspan="2">
<div class="form-label">Idle&nbsp;nodes</div>
<select name="unused_node_list:list" size="10" multiple="multiple" style="width:100%">
<dtml-in getIdleNodeList>
<option value="<dtml-var sequence-item>"><dtml-var sequence-item></option>
</dtml-in>
</select>
</td>
<td>
<input type="submit" name="manage_addToProcessingList:method" value="&gt;"/>
</td>
<td rowspan="2">
<div class="form-label">Processing&nbsp;nodes</div>
<select name="processing_node_list:list" size="10" multiple="multiple" style="width:100%">
<dtml-in getProcessingNodeList prefix="node">
<option value="<dtml-var node_item>"><dtml-var node_item> (#<dtml-var expr="node_index + 1">)</option>
</dtml-in>
</select>
</td>
</tr>
<tr>
<td>
<input type="submit" name="manage_removeFromProcessingList:method" value="&lt;"/>
</td>
</tr>
<tr>
<td align="left" colspan="2">
<div class="form-element">
<input type="submit" class="form-element" name="manage_delNode:method" value=" Delete " />
</div>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td>&nbsp;</td>
<td align="left">
<div class="form-element">
<input type="submit" class="form-element" name="manage_addNode:method" value=" Add ">
</div>
<td>
<p class="form-help">
Every node sharing the same ZODB will register itself to the idle
node list - except the first one which will be automaticaly declared
both <i>Processing node</i> and <i>Distributing node</i>. Registered
nodes can then be made <i>Processing nodes</i> or <i>Idle nodes</i>.
</p>
<p class="form-help">
<b>Important note:</b> Nodes can register themselves, but can not
unregister themselves (for example, a node which IP has changed will
be present twice in the list). It is up to the user to manualy prune
obsolete nodes. If non-existant nodes are present in the
<i>Processing node</i> list, activities will get balanced to those
nodes and never be executed.
</p>
</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td align="left" colspan=2>
<p class="form-help">
Subscribe/Unsubscribe from Timer Service
</p>
</td>
<td>&nbsp;</td>
</tr>
<tr class="list-header">
<td align="left" valign="top" colspan=2>
<div class="form-label">Subscribe/Unsubscribe from Timer Service</div>
</td>
</tr>
<tr>
<td colspan=2>
<div class="form-label">
Status:
<dtml-if isSubscribed>
Subscribed
<dtml-else>
Not Subscribed
</dtml-if>
</dtml-if>
</div>
</td>
</tr>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7