@@ -3,6 +3,12 @@ title: "グリッドのコンポーネント"
3
3
weight : 1
4
4
---
5
5
6
+ {{% notice info %}}
7
+ <i class =" fas fa-language " ></i > There are certain paragaraphs needs translation from
8
+ English to Japanese. Do you speak Japanese? Help us to translate
9
+ it by sending us pull requests!
10
+ {{% /notice %}}
11
+
6
12
![ Grid] ( /images/grid_4.png )
7
13
8
14
## ルーター
@@ -46,17 +52,45 @@ SafariおよびInternet Explorerの場合、作成されるスロットは1つ
46
52
たとえば、WindowsノードにはInternet Explorerをブラウザーオプションとして提供する機能がありますが、
47
53
これはLinuxまたはMacでは不可能です。
48
54
49
- ## セッションマップ
55
+ ## Session Map
56
+
57
+ The Session Map is a data store that keeps the information of the session id and the Node
58
+ where the session is running. It serves as a support for the Router in the process of
59
+ forwarding a request to the Node. The Router will ask the Session Map for the Node
60
+ associated to a session id.
61
+
62
+ ## New Session Queuer, New Session Queue
63
+
64
+ The New Session Queuer is the only
65
+ component which can communicate with the New Session Queue. It handles all queue operations like
66
+ add to manipulate the queue. It has configurable parameters for setting
67
+ the request timeout and request retry interval.
68
+
69
+ The New Session Queuer receives the new session request from the Router and adds it to the queue.
70
+ The queuer waits until it receives the response for the request.
71
+ If the request times out, the request is rejected immediately and not added to the queue.
72
+
73
+ Upon successfully adding the request to the queue, Event Bus triggers an event.
74
+ The Distributor picks up this event and polls the queue. It now attempts to create a session.
75
+
76
+ If the requested capabilities do not exist in any of the registered Nodes, then the request is rejected
77
+ immediately and the client receives a response.
78
+
79
+ If the requested capabilities match the capabilities of any of Node slots, Distributor attempts to get the
80
+ available slot. If all the slots are busy, the Distributor will ask the queuer to add the request
81
+ to the front of the queue. The Distributor receives the request again after the request retry interval.
82
+ It will attempt retries until the request is successful or has timed out.
83
+ If request times out while retrying or adding to the front of the queue its rejected.
50
84
51
- セッションマップは、セッションIDとセッションが実行されているノードの情報を保持するデータストアです。
52
- これは、リクエストをノードに転送するプロセスにおけるルーターのサポートとして機能します。
53
- ルーターは、セッションIDに関連付けられたノードをセッションマップに要求します。
54
- 完全分散モードでGridを開始する場合、セッションマップは、開始する必要がある最初のコンポーネントです。
85
+ After getting an available slot and session creation, the Distributor passes the new session response
86
+ to the New Session Queuer via the Event Bus. The New Session Queuer will respond to the client when it
87
+ receives the event.
55
88
56
- ## イベントバス
89
+ ## Event Bus
57
90
58
- イベントバスは、ノード、ディストリビュータ、およびセッションマップ間の通信パスとして機能します。
59
- Gridは、メッセージを介して内部通信の大部分を行い、高価なHTTP呼び出しを回避します。
91
+ The Event Bus serves as a communication path between the Nodes, Distributor, New Session Queuer, and Session Map.
92
+ The Grid does most of its internal communication through messages, avoiding expensive HTTP calls.
93
+ When starting the Grid in its fully distributed mode, the Event Bus is the first component that should be started.
60
94
61
95
## Gridの役割
62
96
0 commit comments