1. 首頁
  2. 問答
  3. MarkLogic任務服務器狀態

MarkLogic任務服務器狀態

2015-08-26 83 views
0

我們在生產配置中有專用的D節點和E節點組。我試圖收集D節點組中所有主機上任務服務器的請求狀態。我使用xdmp：服務器狀態（HOST_ID，SERVER_ID）其中HOST_ID是我們屬於d-節點第六組一臺主機的ID，和SERVER_ID是taskserver爲d的ID - 節點組。查詢運行得很好，但我對輸出中的一些元素有困惑（見下文）。MarkLogic任務服務器狀態

  1. 是什麼線程和max_threads的元素之間的區別？我查閱了MarkLogic API xdmp：server-status（），看起來他們對這兩個元素都做了相同的描述，這顯然是錯誤的。

  2. request_status元素的總和是否代表正在運行的任務數量？這可能很直觀，但只是想確認一下。

    <server-status xmlns="http://marklogic.com/xdmp/status/server"> 
    <server-id>11927597993558616659</server-id> 
    <host-id>10652389071003024571</host-id> 
    <server-kind>task-server</server-kind> 
    <enabled>true</enabled> 
    <threads>9</threads> 
    <max-threads>16</max-threads> 
    <max-time-limit>3600</max-time-limit> 
    <default-time-limit>600</default-time-limit> 
    <current-time>2015-08-26T04:06:41.622879-04:00</current-time> 
    <request-statuses> 
    <request-status> 
    <request-id>17847109729564550394</request-id> 
    <server-id>11927597993558616659</server-id> 
    <host-id>10652389071003024571</host-id> 
    <transaction-id>11386673421668364533</transaction-id> 
    <canceled>false</canceled> 
    <modules>16882056828749629778</modules> 
    <database>13691199455930504749</database> 
    <root>/</root> 
    <request-kind>invoke</request-kind> 
    <request-text>/MarkLogic/cpf/triggers/on-state-enter.xqy</request-text> 
    <update>false</update> 
    <start-time>2015-08-26T04:06:41.621354-04:00</start-time> 
    <time-limit>600</time-limit> 
    <max-time-limit>3600</max-time-limit> 
    <user>15525372533614500271</user> 
    <trigger-depth>0</trigger-depth> 
    <expanded-tree-cache-hits>0</expanded-tree-cache-hits> 
    <expanded-tree-cache-misses>0</expanded-tree-cache-misses> 
    <request-state>running</request-state> 
    <profiling-allowed>true</profiling-allowed> 
    <profiling-enabled>false</profiling-enabled> 
    <debugging-allowed>true</debugging-allowed> 
    <debugging-status>detached</debugging-status> 
    <retry-count>0</retry-count> 
    </request-status> 
    <request-status> 
    <request-id>8474714682726605430</request-id> 
    <server-id>11927597993558616659</server-id> 
    <host-id>10652389071003024571</host-id> 
    <transaction-id>8554209989266201299</transaction-id> 
    <canceled>false</canceled> 
    <modules>16882056828749629778</modules> 
    <database>13691199455930504749</database> 
    <root>/</root> 
    <request-kind>invoke</request-kind> 
    <request-text>/MarkLogic/cpf/triggers/on-state-enter.xqy</request-text> 
    <update>true</update> 
    <start-time>2015-08-26T04:06:41.483786-04:00</start-time> 
    <time-limit>600</time-limit> 
    <max-time-limit>3600</max-time-limit> 
    <user>15525372533614500271</user> 
    <trigger-depth>0</trigger-depth> 
    <expanded-tree-cache-hits>20</expanded-tree-cache-hits> 
    <expanded-tree-cache-misses>0</expanded-tree-cache-misses> 
    <request-state>running</request-state> 
    <profiling-allowed>true</profiling-allowed> 
    <profiling-enabled>false</profiling-enabled> 
    <debugging-allowed>true</debugging-allowed> 
    <debugging-status>detached</debugging-status> 
    <retry-count>0</retry-count> 
    </request-status> 
    <request-status> 
    <request-id>6530741740134403011</request-id> 
    <server-id>11927597993558616659</server-id> 
    <host-id>10652389071003024571</host-id> 
    <transaction-id>14792921325069589956</transaction-id> 
    <canceled>false</canceled> 
    <modules>16882056828749629778</modules> 
    <database>13691199455930504749</database> 
    <root>/</root> 
    <request-kind>invoke</request-kind> 
    <request-text>/MarkLogic/cpf/triggers/on-state-enter.xqy</request-text> 
    <update>true</update> 
    <start-time>2015-08-26T04:06:41.52227-04:00</start-time> 
    <time-limit>600</time-limit> 
    <max-time-limit>3600</max-time-limit> 
    <user>15525372533614500271</user> 
    <trigger-depth>0</trigger-depth> 
    <expanded-tree-cache-hits>20</expanded-tree-cache-hits> 
    <expanded-tree-cache-misses>0</expanded-tree-cache-misses> 
    <request-state>running</request-state> 
    <profiling-allowed>true</profiling-allowed> 
    <profiling-enabled>false</profiling-enabled> 
    <debugging-allowed>true</debugging-allowed> 
    <debugging-status>detached</debugging-status> 
    <retry-count>0</retry-count> 
    </request-status> 
    <request-status> 
    <request-id>9441948619847315123</request-id> 
    <server-id>11927597993558616659</server-id> 
    <host-id>10652389071003024571</host-id> 
    <transaction-id>13501074757179797206</transaction-id> 
    <canceled>false</canceled> 
    <modules>16882056828749629778</modules> 
    <database>13691199455930504749</database> 
    <root>/</root> 
    <request-kind>invoke</request-kind> 
    <request-text>/MarkLogic/cpf/triggers/on-status-enter.xqy</request-text> 
    <update>false</update> 
    <start-time>2015-08-26T04:06:41.594876-04:00</start-time> 
    <time-limit>600</time-limit> 
    <max-time-limit>3600</max-time-limit> 
    <user>15525372533614500271</user> 
    <trigger-depth>0</trigger-depth> 
    <expanded-tree-cache-hits>0</expanded-tree-cache-hits> 
    <expanded-tree-cache-misses>0</expanded-tree-cache-misses> 
    <request-state>running</request-state> 
    <profiling-allowed>true</profiling-allowed> 
    <profiling-enabled>false</profiling-enabled> 
    <debugging-allowed>true</debugging-allowed> 
    <debugging-status>detached</debugging-status> 
    <retry-count>0</retry-count> 
    </request-status> 
    <request-status> 
    <request-id>3267724788720707644</request-id> 
    <server-id>11927597993558616659</server-id> 
    <host-id>10652389071003024571</host-id> 
    <transaction-id>16009199203479096620</transaction-id> 
    <canceled>false</canceled> 
    <modules>16882056828749629778</modules> 
    <database>13691199455930504749</database> 
    <root>/</root> 
    <request-kind>invoke</request-kind> 
    <request-text>/MarkLogic/cpf/triggers/on-state-enter.xqy</request-text> 
    <update>true</update> 
    <start-time>2015-08-26T04:06:41.483616-04:00</start-time> 
    <time-limit>600</time-limit> 
    <max-time-limit>3600</max-time-limit> 
    <user>13094335114653925163</user> 
    <trigger-depth>0</trigger-depth> 
    <expanded-tree-cache-hits>20</expanded-tree-cache-hits> 
    <expanded-tree-cache-misses>0</expanded-tree-cache-misses> 
    <request-state>running</request-state> 
    <profiling-allowed>true</profiling-allowed> 
    <profiling-enabled>false</profiling-enabled> 
    <debugging-allowed>true</debugging-allowed> 
    <debugging-status>detached</debugging-status> 
    <retry-count>0</retry-count> 
    </request-status> 
</request-statuses> 
<request-rate>16.11519</request-rate> 
<queue-size>0</queue-size> 
<queue-limit>100000</queue-limit> 
<expanded-tree-cache-hits>241396964</expanded-tree-cache-hits> 
<expanded-tree-cache-misses>65339949</expanded-tree-cache-misses> 
<expanded-tree-cache-hit-rate>161.5713</expanded-tree-cache-hit-rate> 
<expanded-tree-cache-miss-rate>8.095861</expanded-tree-cache-miss-rate> 
<fs-program-cache-hits>26819890</fs-program-cache-hits> 
<fs-program-cache-misses>26819890</fs-program-cache-misses> 
<db-program-cache-hits>3632389</db-program-cache-hits> 
<db-program-cache-misses>3632389</db-program-cache-misses> 
<fs-main-module-seq-cache-hits>4694</fs-main-module-seq-cache-hits> 
<fs-main-module-seq-cache-misses>4694</fs-main-module-seq-cache-misses> 
<db-main-module-seq-cache-hits>15144</db-main-module-seq-cache-hits> 
<db-main-module-seq-cache-misses>15144</db-main-module-seq-cache-misses> 
<fs-lib-module-cache-hits>1102986</fs-lib-module-cache-hits> 
<fs-lib-module-cache-misses>1102986</fs-lib-module-cache-misses> 
<db-lib-module-cache-hits>14221</db-lib-module-cache-hits> 
<db-lib-module-cache-misses>14221</db-lib-module-cache-misses>

來源

2015-08-26 Arnab Biswas

回答

1

是該文檔是錯的，我會的文件上的錯誤，他們的意思你可能認爲。 max-threads是可以運行的最大線程數，threads是當前運行的線程數。請求狀態的總和（通常）應該與線程匹配。由於線程處於「池」中，因此有些時段的總和不完全匹配。

你可以試試這個簡單的測試。

for $i in 1 to 1000 return 
xdmp:spawn-function(function() { xdmp:sleep(10000) })

它應該立即返回填充1000個任務的隊列。

然後運行這個偶爾

xdmp:server-status(xdmp:host(),xdmp:server("TaskServer")) ! (./*:threads,count(./*:request-statuses/*:request-status))

來源

2015-08-26 11:49:01 DALDEI

+0

非常感謝@DALDEI。我一直認爲請求狀態的總和小於線程的總和。我不確定我完全理解這是如何解釋的線程彙集的事實。道歉，如果我失去了明顯的東西！ –

+0

max_threads僅表示將有一定數量的並行運行工作線程用於清除任務服務器隊列，並且該數字不能超過max_threads。 max_threads表示線程池大小，可重用的工作線程對象的庫。線程告訴有多少實際活動.. – grtjn

+0

謝謝。我只是認爲request_status元素的數量應該與線程元素的值匹配，如果它們實質上表示相同的信息。 –

相關問題

 相關問題