簡體   English   中英

當執行相同的遍歷查詢時,Arango會隨機重新啟動

[英]Arango restarts on a random basis when same traversal query is performed

我正在運行從節點服務器到安裝了Arango的Ubuntu AWS實例的一系列同時請求。 Arangod是版本3.1.7

一切都運行良好幾周,但現在:

在隨機的基礎上,我在執行查詢時從節點獲得{Error:socket hang up},總是相同的,並且arango似乎重新啟動,因為我得到{錯誤:連接ECONNREFUSED}所有其他查詢而。 它發生在6次中的1次,盡管我的數據在查詢之間沒有變化。

Web界面日志非常少,似乎無法解釋出現了什么問題。 Arangod似乎創建了一個日志文件,但很難解釋。 所有服務器指標都很好。

您對如何在這個問題上取得進展有什么想法? 我的數據損壞了嗎? 我該怎么知道?

這是我的日志文件的內容:

2017-02-22T16:24:57Z [11449] INFO ArangoDB 3.1.7 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 5.0.71.39, OpenSSL 1.0.1f 6 Jan 2014
2017-02-22T16:24:57Z [11449] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-02-22T16:24:57Z [11449] INFO Authentication is turned on
2017-02-22T16:24:57Z [11449] INFO Authentication system only
2017-02-22T16:24:57Z [11449] INFO Authentication for unix sockets is turned on
2017-02-22T16:24:57Z [11449] INFO file-descriptors (nofiles) hard limit is 131072, soft limit is 131072
2017-02-22T16:24:57Z [11449] INFO running WAL recovery (1 logfiles)
2017-02-22T16:24:57Z [11449] INFO replaying WAL logfile '/vol/data/standalone/journals/logfile-44002553.db' (1 of 1)
2017-02-22T16:24:57Z [11449] INFO WAL recovery finished successfully
2017-02-22T16:24:57Z [11449] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-02-22T16:24:57Z [11449] INFO In database '_system': Database is up-to-date (30107/standalone/existing)
2017-02-22T16:24:57Z [11449] INFO In database 'X-DB': Database is up-to-date (30107/standalone/existing)
2017-02-22T16:24:57Z [11449] INFO using endpoint 'http+tcp://0.0.0.0:8529' for non-encrypted requests
2017-02-22T16:24:58Z [11449] INFO Please note that a new bugfix version '3.1.11' is available
2017-02-22T16:24:58Z [11449] INFO ArangoDB (version 3.1.7 [linux]) is ready for business. Have fun!

而且:

2017-02-22T16:24:57Z [1311] ERROR {startup} child 11302 died a horrible death, signal 11
2017-02-22T16:27:57Z [1311] ERROR {startup} child 11449 died a horrible death, signal 11

我相信引起麻煩的查詢是:

RETURN (
FOR i, j, k IN 0..3 INBOUND "Hint/26427214" GRAPH "X-graph"
FILTER k.vertices[1]._id LIKE "Drop/%"
AND k.vertices[2]._id LIKE "Hint/%"
AND k.vertices[3]._id LIKE "Drop/%"
FILTER k.vertices[1].hostname != k.vertices[3].hostname
FILTER k.vertices[2].type == "article"
SORT k.vertices[2].createdAt DESC
LIMIT 0, 1
RETURN UNION (
FOR v, e, p IN 0..2 INBOUND k.vertices[2]._id GRAPH "X-graph"
FILTER p.vertices[1]._id LIKE "Source/%"
AND p.vertices[2]._id LIKE "Twittos/%"
RETURN { key: p.vertices[0]._key, retweets: p.vertices[0].retweets, title: p.vertices[0].title, type: p.vertices[0].type, content: p.vertices[0].content, image: p.vertices[0].image, source: { key: p.vertices[1]._key, name: p.vertices[1].name, screenname: p.vertices[2].screenname, image: p.vertices[2].image }},
FOR v, e, p IN 0..1 INBOUND k.vertices[2]._id GRAPH "X-graph"
FILTER p.vertices[1]._id LIKE "Source/%"
RETURN { key: p.vertices[0]._key, retweets: p.vertices[0].retweets, title: p.vertices[0].title, type: p.vertices[0].type, content: p.vertices[0].content, image: p.vertices[0].image, source: { key: p.vertices[1]._key, name: p.vertices[1].name }},
FOR v, e, p IN 0 INBOUND k.vertices[2]._id GRAPH "X-graph" RETURN { key: p.vertices[0]._key, retweets: p.vertices[0].retweets, title: p.vertices[0].title, type: p.vertices[0].type, image: p.vertices[0].image, content: p.vertices[0].content })[0] )[*]

經過大量的研究,我試圖簡單地升級到arangod 3.1.11。 問題似乎已經消失。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM