ArangoDB3.4.0 Connection reset #7785
Comments
|
Hi, |
|
Please edit your initial post and fill out the template with the ArangoDB version in use etc. |
|
Hi @wqxcloud, It would be nice if you can fill out the template with as much information as possible. In addition may you answer dothebart's questions Thanks |
I`m so sorry for look it now。 i have update it。So much configuration i used the default（do not have to change it） |
I`m so sorry for look it now。 i have update it。So much configuration i used the default（do not have to change it） |
I`m so sorry for look it now。 i have update it |
|
@wqxcloud Did you start with 3.4.0 and a fresh data directory? Then the default engine would be RocksDB. If you upgraded with data from 3.3.x, then it would be MMFiles. |
I start with 3.4.0 and a fresh data directory. |
|
I need your help,Thanks |
|
@wqxcloud : I am happy to look into this, but without further information I doubt we can make much progress here. As the ticket does not contain any information about indexes, cardinality etc. of the underlying collections nor about the bind parameters used, I tried setting up the collections locally with some dummy data and used some test bind parameters. bind = {account:"abc", offset: 10, limit: 1005};
q = `FOR shuoshuo IN t_shuoshuo SORT shuoshuo.date DESC LIMIT @offset, @limit RETURN { shuoshuo: shuoshuo, likenumber: (FOR shuoshuolike IN t_shuoshuolike FILTER shuoshuolike.shuoshuoId == shuoshuo._key COLLECT WITH COUNT INTO likenumber RETURN likenumber) , ismyliked: (FOR shuoshuolike IN t_shuoshuolike FILTER shuoshuolike.shuoshuoId == shuoshuo._key AND shuoshuolike.account == @account COLLECT WITH COUNT INTO ismyliked RETURN ismyliked) , commentnumber: (FOR shuocomment IN t_shuoshuocomment FILTER shuocomment.shuoshuoId == shuoshuo._key COLLECT WITH COUNT INTO commentnumber RETURN commentnumber), replynumber: (FOR shuoreply IN t_shuoshuocommentreply FILTER shuoreply.shuoshuoId == shuoshuo._key COLLECT WITH COUNT INTO replynumber RETURN replynumber) , userinfo: (FOR userinfo IN t_userinfo FILTER userinfo.account == shuoshuo.account RETURN {avatarurl:userinfo.avatarurl,nickname:userinfo.nickname,online:userinfo.online} )}`;
db._explain(q, bind);
db._query(q, bind);At least locally this does not trigger any problem. It would there be helpful if you could try running the query in ArangoDB's web UI with a fixed set of bind parameters to see if that triggers the problem. Additionally it would be helpful to see what indexes are available on the underlying collection and how the data is structured. |
|
Hi, @wqxcloud, Just sending a quick follow up. Did you have a chance to run the query in ArangoDB's web UI with a fixed set of parameters as jsteemann suggested? You can generate a debug package by clicking on "Create debug package" button. This package will help us further investigate the issue. Thanks! |
|
@wqxcloud I am closing this issue for now since we have not heard back from you in a while. |
My Environment
[root@xu arangodb3]# lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.6.1810 (Core)
Release: 7.6.1810
Codename: Core
Component, Query & Data
Affected feature:
AQL query (if applicable):@query("FOR shuoshuo IN t_shuoshuo SORT shuoshuo.date DESC #pageable "
+ " RETURN {"
+ " shuoshuo: shuoshuo,"
+ " likenumber: (FOR shuoshuolike IN t_shuoshuolike"
+ " FILTER shuoshuolike.shuoshuoId == shuoshuo._key"
+ " COLLECT WITH COUNT INTO likenumber RETURN likenumber) ,"
+ " ismyliked: (FOR shuoshuolike IN t_shuoshuolike"
+ " FILTER shuoshuolike.shuoshuoId == shuoshuo._key AND shuoshuolike.account == @account"
+ " COLLECT WITH COUNT INTO ismyliked RETURN ismyliked) ,"
+ " commentnumber: (FOR shuocomment IN t_shuoshuocomment"
+ " FILTER shuocomment.shuoshuoId == shuoshuo._key"
+ " COLLECT WITH COUNT INTO commentnumber RETURN commentnumber), " +
" replynumber: (FOR shuoreply IN t_shuoshuocommentreply"
+ " FILTER shuoreply.shuoshuoId == shuoshuo._key"
+ " COLLECT WITH COUNT INTO replynumber RETURN replynumber) ,"
+ " userinfo: (FOR userinfo IN t_userinfo"
+ " FILTER userinfo.account == shuoshuo.account "
+ " RETURN {avatarurl:userinfo.avatarurl,nickname:userinfo.nickname,online:userinfo.online} )"
+ "}")
Page findAllShuoShuoWithPage(@param("pageable") Pageable pageable,@param("account") long account);
AQL explain (if applicable):
Dataset:
Replication Factor & Number of Shards (Cluster only):
Steps to reproduce
Problem:
nested exception is com.arangodb.ArangoDBException: java.util.concurrent.ExecutionException: com.arangodb.ArangoDBException: java.net.SocketException: Connection reset] with root cause
java.net.SocketException: Connection reset
Expected result:
The text was updated successfully, but these errors were encountered: