neo4j-dotnet-driver: Big requests do not complete

On my solution if I run: session.Run("match(n) return n limit 5000").ToList() It works

if I run: session.Run("match(n) return n limit 10000").ToList() It never completes

It works with 1.5.0-alpha01 (result comes very quickly) but not with the upper versions (final 1.5.0 included).

(test with dotnet core 2 in xunit unit test)

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 29 (11 by maintainers)

Most upvoted comments

The rest of this issue, apart from the fixes we’ve made earlier in the driver, is found to be related with memory consumption of the server. It is the server that terminates connections based on an OutOfDirectMemory exception, and it is the point where client receives an unexpected end of stream. You can tune server’s memory limits through neo4j.conf.

We’ve addressed this memory pressure on the bolt server with PR #10433 and it will be part of 3.4.0 server release.

I am now closing this issue, and we’ll be releasing a 1.5.1 version soon that includes driver side fixes.

Thanks,

Drivers Team

ali-ince on Nov 14, 2017