Added: 
MaxNoOfOrderedIndexes = 5000    # Needed to add more tables
MaxNoOfUniqueHashIndexes = 5000 # Needed to add more tables

In the management node, this seems to be working fine.

I have this configuration running with some publishers. I will keep it running for a while to check that the EFD won't have any issues after storing data.

Tried to create the whole EFD schema but I had issues to new constraints that the NDB engine has over innoDB (512 attributes per table at max).  We will need to find a solution to this issue, either add a new constraint or create additional tables as "arrays"

Created a Jira ticket to Dave to review the last comment.:

https://jira.lsstcorp.org/browse/DM-17204

It's been working for a week now. I couldn't create all the scheme due to ndb limitation in table size but that is under review now. 

To test you can ssh to tcs@139.229.162.113 (nice password), go to the database:
>mysql -uefduser -p 
and do a 

>show tables 

Also if you do multiple time a: 

mysql>select count( *) from ATMCS_mountEncoders; 

you can see that the data keeps increasing.

You can also check Andres V grafana to see EFD performance in: 

http://gs-grafana-node-01.po.us.lsst.org:3000/d/N-bxMeUiz/efd-monitoring?refresh=5s&orgId=1

User and pass will be sent internally 

example plot: 

Increased capacity configured and tested