Limit of 4711 Ndbs per connection

[jdduncan]

The NDB API imposes a limit on the number of Ndb objects that can be used in one Ndb_cluster_connection. This limit is currently 4711 (MAX_NO_THREADS in TransporterFacade.hpp).

Node.JS is designed to allow tens of thousands of concurrent clients, and each client session uses one Ndb object, so we may start to encounter this limit. I am opening this issue preemptively so people are aware of the situation.

[jdduncan]

When you encounter this limit you see error 4105 "Too many Ndb objects".

[CraigLRussell]

We can look at connection pooling to solve this problem "permanently".

Craig

On Jul 22, 2013, at 12:18 PM, John David Duncan wrote:

The NDB API imposes a limit on the number of Ndb objects that can be used in one Ndb_cluster_connection. This limit is currently 4711 (MAX_NO_THREADS in TransporterFacade.hpp).

Node.JS is designed to allow tens of thousands of concurrent clients, and each client session uses one Ndb object, so we may start to encounter this limit. I am opening this issue preemptively so people are aware of the situation.

—
Reply to this email directly or view it on GitHub.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!