neo4j/cloud — Issue #4: Consistent timeouts during selects
Author: williammincy
Created: 2012-02-07 00:30:00+00:00
State: open

Hi, I'm running the Neo4J service on Heroku and am getting timeouts on selects when they are run from uploaded code but run fine on my Development machine. The query isn't a large one, I currently have scaled down the DB to around 2,000 Nodes, 7,600 properties, 5 relationships, and around 400 cached nodes.

The query I'm initiating uses Cypher and I am able to enter the query into the web-based data browser and I get results very fast and with valid data. Running the query from my Dev machine also works fine to pull down the query results. It's only when I put this onto Heroku that things become problematic.

Here is the log message I'm seeing when I do the query
`2012-02-06T19:51:37+00:00 heroku[router]: Error H12 (Request timeout) -> GET api.domain.com/yz/conns dyno=web.1 queue= wait= service=30000ms status=503 bytes=0`

The Cypher query is similar to the following:
`START badge=node:by_type(nodetype='badge') MATCH (badge)<-[:IS_A]-(a) WHERE badge.name = 'sherrif' RETURN a.uid, a.fname, a.lname, a.created ORDER BY a.created DESC`

I have also changed this to pull down objects rather than properties only with the same results:
`START badge=node:by_type(nodetype='badge') MATCH (badge)<-[:IS_A]-(a) WHERE badge.name = 'sherrif' RETURN a`

What could be the cause of this? And is the fix something I can enact or is this a service-level issue?

Thanks,
william.mincy