当执行相同的遍历查询时,Arango 随机重启
Arango restarts on a random basis when same traversal query is performed
我是 运行 从节点服务器到安装了 Arango 的 Ubuntu AWS 实例的一系列同时请求。 Arangod 是版本 3.1.7
几周来一切正常,但现在:
在随机的基础上,我在执行查询时从节点收到 {Error: socket hang up},总是相同的,并且当我收到 {Error: connect ECONNREFUSED} 时,arango 似乎重新启动其他查询一会儿。
它发生了 6 次中的 1 次,尽管我的数据在查询之间没有改变。
Web Interface 日志非常少,似乎无法解释问题出在哪里。 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。问题好像没了。
我是 运行 从节点服务器到安装了 Arango 的 Ubuntu AWS 实例的一系列同时请求。 Arangod 是版本 3.1.7
几周来一切正常,但现在:
在随机的基础上,我在执行查询时从节点收到 {Error: socket hang up},总是相同的,并且当我收到 {Error: connect ECONNREFUSED} 时,arango 似乎重新启动其他查询一会儿。 它发生了 6 次中的 1 次,尽管我的数据在查询之间没有改变。
Web Interface 日志非常少,似乎无法解释问题出在哪里。 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。问题好像没了。