The uses the NDB to store user-provided data. The stores the entries in NDB Cluster using shared data model which allows for simultanious LDAP/SQL datastore access. ds-cfg-ndb-backend ds-cfg-backend presence aci equality entryUUID equality objectClass ordering ds-sync-hist cn=Index org.opends.server.backends.ndb.BackendImpl Specifies the NDB connect string. IP addresses or hostnames with portnumbers may be provided. localhost ds-cfg-ndb-connect-string Specifies the SQL connect string. IP addresses or hostnames with portnumbers may be provided. localhost ds-cfg-sql-connect-string Specifies the SQL database user on whose behalf the connection is being made. SQL user name may be provided. root ds-cfg-sql-user Specifies the SQL database user password. SQL user password may be provided. ds-cfg-sql-passwd Specifies the SQL/NDB database name. SQL/NDB database name may be provided. ldap ds-cfg-ndb-dbname Specifies the number of NDB connections. Logical connections made to NDB Cluster. 4 ds-cfg-ndb-num-connections Specifies the number of threads that is used for concurrent NDB processing. This should generally be equal to the number of worker threads. 24 ds-cfg-ndb-thread-count Specifies the attribute length. This should reflect SQL/NDB attribute column length. 128 ds-cfg-ndb-attr-len Specifies the blob attribute. This should specify which attribute to treat as a blob. ds-cfg-ndb-attr-blob Specifies the number of times that the server should retry an attempted operation in the backend if a deadlock results from two concurrent requests that interfere with each other in a conflicting manner. A value of "0" indicates no limit. 10 ds-cfg-deadlock-retry-limit Specifies the size (in number of entries) of the queue that is used to hold the entries read during an LDIF import. Changes do not take effect for any import that may already be in progress. 100 ds-cfg-import-queue-size Specifies the number of threads that is used for concurrent processing during an LDIF import. This should generally be a small multiple (for example, 2x) of the number of CPUs in the system for a traditional system, or equal to the number of CPU strands for a CMT system. Changes do not take effect for any import that may already be in progress. 8 ds-cfg-import-thread-count Specifies the maximum number of entries that is allowed to match a given index key before that particular index key is no longer maintained. This property is analogous to the ALL IDs threshold in the Sun Java System Directory Server. Note that this is the default limit for the backend, and it may be overridden on a per-attribute basis. A value of 0 means there is no limit. If any index keys have already reached this limit, indexes need to be rebuilt before they are allowed to use the new limit. 4000 ds-cfg-index-entry-limit