Hello list,

we use an application to connect via NDB API to the cluster.

If we start some threads of this application (C++) we get the following kind of
errors:

Ndb error: 266 Time-out in NDB, probably caused by deadlock commit(NO_WRITE)
failed (transaction level)

Ndb error: 4025 Node failure caused abort of transaction commit(NO_WRITE)failed
(transaction level)

Ndb error: 4012 Request ndbd time-out, maybe due to high load or communication
problems commit(NO_WRITE) failed (transaction level)

The application does a mixture of read /write operations on some tables (always
the same set of tables).

Is this a problem of the application or do we need some tuning on the cluster
parameters (for instance MaxNumberofConcurrentTransaction) ?

Joerg