Thanks for you quick response, I have already restart the server, I need to wait the problem situation, coz I can't re-product it.
I have checked the py2neo log: [2015-09-16 07:27:19] [INFO] [28681:MainThread] [http:310 send()] > GET http > ://10.181.205.198:8474/db/data/ > [2015-09-16 07:27:37] [INFO] [28681:MainThread] [http:306 send()] ~ > Reconnecting (timeout) > > Normally, it response 200 OK within 1 second. Not only this REST API, but all encounter time out for hours, not one moment. And I'm sure the IP and port are certainly right, coz It have run for long time, and after restart the neo4j server, I get the log: [2015-09-16 07:47:16] [INFO] [7557:MainThread] [http:310 send()] > GET http://10.181.205.198:8474/db/data/ [2015-09-16 07:47:16] [INFO] [7557:MainThread] [http:511 __init__()] < 200 OK [785] How's that possible after server running normal for hours (have response millions of read/write REST API normally), and suddenly goes time out? and seems not recover to normal... On Wednesday, September 16, 2015 at 8:22:40 AM UTC+8, Michael Hunger wrote: > > Hmm, > > 1. first of all you should use the / at the end otherwise you also measure > redirect time. > 2. you should use accept header of application/json > as you don't want to measure html generation. > > Please try that and report back, for me i does > > time curl -L http://neo.jexp.de:12474/db/data/ > { > "extensions" : { }, > "node" : "http://neo.jexp.de:12474/db/data/node";, > "node_index" : "http://neo.jexp.de:12474/db/data/index/node";, > "relationship_index" : " > http://neo.jexp.de:12474/db/data/index/relationship";, > "extensions_info" : "http://neo.jexp.de:12474/db/data/ext";, > "relationship_types" : " > http://neo.jexp.de:12474/db/data/relationship/types";, > "batch" : "http://neo.jexp.de:12474/db/data/batch";, > "cypher" : "http://neo.jexp.de:12474/db/data/cypher";, > "indexes" : "http://neo.jexp.de:12474/db/data/schema/index";, > "constraints" : "http://neo.jexp.de:12474/db/data/schema/constraint";, > "transaction" : "http://neo.jexp.de:12474/db/data/transaction";, > "node_labels" : "http://neo.jexp.de:12474/db/data/labels";, > "neo4j_version" : "2.3-SNAPSHOT" > } > real 0m0.055s > user 0m0.004s > sys 0m0.004s > > > Am 16.09.2015 um 02:12 schrieb Singleton Chiu <[email protected] > <javascript:>>: > > Just Now, I encounter the same situation, here's the more specific info, > I would very much appreciate for your time. > > neo4j v2.2.3 java1.7 on linux 64bit 96GB mem > > node nums > Node ID 9058830 > Property ID 80189638 > Relationship ID 37459428 > > > config: > org.neo4j.server.webserver.address=0.0.0.0 > org.neo4j.server.webserver.port=8474 > remote_shell_port=1390 > > > > Problem: REST API suddenly very slow response, situation for hours. When I > restart the server, API return to normal. > > $time wget localhost:8474/db/data > --2015-09-16 07:36:09-- http <http://localhost:8474/db/data>: > <http://localhost:8474/db/data>//localhost:8474/db/data > <http://localhost:8474/db/data> > Resolving localhost... 127.0.0.1 > Connecting to localhost|127.0.0.1|:8474... connected. > HTTP request sent, awaiting response... 302 Found > Location: http <http://localhost:8474/db/data/>: > <http://localhost:8474/db/data/>//localhost:8474/db/data/ > <http://localhost:8474/db/data/> [following] > --2015-09-16 07:36:43-- http <http://localhost:8474/db/data/>: > <http://localhost:8474/db/data/>//localhost:8474/db/data/ > <http://localhost:8474/db/data/> > Reusing existing connection to localhost:8474. > HTTP request sent, awaiting response... 200 OK > Length: 730 [application/json] > Saving to: `index.html.1' > > 100%[===========================================================================================================================================>] > > 730 --.-K/s in 0s > > 2015-09-16 07:36:43 (60.4 MB/s) - `index.html.1' saved [730/730] > > real 0m34.547s > user 0m0.001s > sys 0m0.002s > > > See, it took 34s to get /db/data/ > > But, shell works just fine! > > > > $bin/neo4j-shell -port 1390 > Welcome to the Neo4j Shell! Enter 'help' for a list of commands > NOTE: Remote Neo4j graph database service 'shell' at port 1390 > > neo4j-sh (?)$ match (n:entity) return n limit 1; > > +--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | n > > | > > +--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | Node[5161]{xxxxxxxx} > > +--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > 1 row > 19 ms > > Here's network IO: > > > > sar -n DEV 1 3 > Average: IFACE rxpck/s txpck/s rxbyt/s txbyt/s rxcmp/s > txcmp/s rxmcst/s > Average: lo 9.15 9.15 3347.80 3347.80 0.00 > 0.00 0.00 > Average: eth0 33.56 32.20 2277.63 5508.14 0.00 > 0.00 0.68 > Average: eth1 35.93 36.95 2694.24 3387.80 0.00 > 0.00 0.00 > Average: bond0 69.15 69.15 4949.49 8895.93 0.00 > 0.00 0.68 > > > And When I did nothing except restart the neo4j server, The REST API looks > just fine: > > > $bin/neo4j restart > Stopping Neo4j Server [15300 > ]................................................... done > Starting > > ... -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
