Timeouts are not on the tasks themselves, but rather on the task node.
超时不是发生在任务自身，而是发生在任务节点上。
A snippet node computes a value or performs some task.
代码片段节点计算一个值或执行某一任务。
When you select the task, the offending node will be highlighted.
当您选择任务时，存在错误的节点将被突出显示。
This handler first pegs the escalation counter and then completes a task instance, associated with this node.
这个处理器首先记录上报计数器，接着完成此节点关联的任务实例。
Scaling down is like a failback operation without the task of bringing the primary node up.
向下扩展就像退回操作，其中没有将主节点置于在线的任务。
The task also has a start node, however, this node is optional and does not change the execution semantics of the task, which can only begin execution when the input is available.
该任务也有一个开始节点，不过，这个节点是可选的，不会改变任务的执行语义，这个任务只有在该输入可用的情况下才会开始执行。
The basic business process originally only consists of a receive node, a human task, a snippet, and a reply activity.
基础业务流程最初仅由一个接收节点、一个人工任务和一个回复活动构成。
The first thing you need to do is retrieve the process template information including its human task node activities.
您首先需要做的是获取流程模板信息，包括其人工任务节点活动。
Timeout handler (Listing 16) is invoked when a task node timer is fired.
任务节点计时器触发调用的超时处理器(清单16)。
Failover is the planned or unplanned shutdown of the primary system and includes the accompanying task of bringing a standby node online to take over the processing load.
故障转移是主系统在计划内或计划外的关闭，并包括完成将备用节点置于在线以接管处理负载的任务。
The worker node processes that smaller task, and passes the answer back to the master node.
工作者节点处理这些小任务，把结果返回给主节点。
This step sets up a basic nd environment, and is the task that makes the node a part of the nd environment.
该步骤将建立基本ND环境，且使该节点作为ND环境的组成部分。
Using a stop node instead would not be a correct solution, because it would immediately end the whole process and prevent execution of Task 4.
此处如果换成停止节点将是一个错误的解决方案，因为它会立即终止整个流程，Task4将不会执行。
However, the process will not release its data in the simulation because the parallel branches involving Task 2 and Task 3 do not end with a stop node.
不过，在进行模拟时，该流程将不会释放它的数据，因为涉及Task2和Task3的分支不是以停止节点结束的。
The end node to which Task 3 previously connected is no longer needed.
现在已经不再需要Task3先前连接的结束节点了。
Immediately following the start node, a decision represents three alternative branches in the process flow that eventually lead to a join preceding Task 5.
在开始节点后，紧跟一个decision，它表示流程流中的三个可选分支，这些分支最终引向Task 5之前的join。
This node is connected to Task 1, symbolized by a yellow rectangle with rounded corners.
此节点连接到Task1，后者用黄色的圆角矩形表示。
To accomplish this task, you place an entry in a special configuration file known as the node directory.
为了完成这项任务，首先要在一个称为节点目录(node directory)的专用配置文件中添加一个条目。
The user captured the two final events that the task triggers after successful execution in a decision with two outgoing branches that directly end in a stop node.
当在一个带有两个传出分支（这两个分支直接终止于某个停止节点）的decision 中成功执行之后，用户会捕获由任务触发的那两个最终事件。
Using Action handler, attached to a task node enter event to create multiple node instances 10, based on the process instance variables.
使用动作处理器(Action handler)：附加到任务节点的进入事件(enter event)，基于流程实例变量创建多个节点实例10。
Choose task create virtual server under the Hardware and Software node, and create a virtual server on host blade2; choose the master image template you just created.
选择Hardwareand Soft ware节点下的CreateVirtualServer任务，并在blade2主机上创建一个虚拟服务器；选择刚刚创建的主映像模板。
Task instance completion is accompanied by a transition (typically back to task node).
任务实例的完成伴随有一个变迁(一般是回到任务节点)。
This use of the stop node is correct, because task 4 is the last executing task of this process and no other activities execute in parallel.
在此处使用停止节点是正确的，因为Task4是该流程执行的最后一个任务，而且没有与之并行执行的活动。
In the Reduce process, the master node then takes the answers of all the sub-tasks and combines them to get the output, which is the result of the original task.
然后，在缩减过程中，主节点把所有子任务的结果组合成输出，这就是原任务的结果。
You should replace a join that only has start nodes as input with a single start node that directly connects to a task or subprocess.
您应当用一个直接连接到某个任务或子流程的开始节点，替换一个只使用开始节点作为输入的join。
How to end on first async parallel task completion in Node?
如何结束第一异步并行任务的节点？
There are two main factors, the node load and the capability, which affect task distribution.
任务分配的主要因素包括服务节点的处理能力与服务节点实际负载两个部分。
As heterogeneous systems handling capacity of each node differences, task allocation strategy will seriously affect the quality of the system scalability.
由于异构系统各节点处理能力的差异，任务分配策略的好坏将严重影响系统的可扩展性。
Network load balancing network traffic is evenly distributed to the extent possible to complete the same task several of the server or network node, thus part of the network nodes to avoid overload.
网络中的负载均衡就是将网络的流量尽可能均匀分配到几个能完成相同任务的服务器或网络节点上，由此来避免部分网络节点过载。
Because the intermediate nodes have to bear the extra task, this article increases the inner node density of the network approach to balance the node energy consumption in sensoring field.
因为中间节点要承担多余的转发任务，本文中采用增加网络内层节点密度的办法来均衡各个位置的节点能量消耗。
应用推荐