ndb | improved debugging experience for Node.js | Code Inspection library

Using Puppeteer version: "9.0.0"

Unfortunately debugging in chrome dev tools does not work at all with this puppeteer version. So I resorted to NDB. Using NDB I can breakpoint anywhere apart from inside page.evaluate function and page.$$eval().

Running the script with ndb:

My Linux Server is ubuntu 20 MySQL Cluster Management Server mysql-8.0.23 ndb-8.0.23 MySQL distrib mysql-8.0.23 ndb-8.0.23, for Linux (x86_64)

When I try to start(command：ndb_mgmd -f config.ini --ndb-nodeid=11) the mysql cluster mgmd node, it always show the error message Could anyone help me? Thanks

I'm writing a protocol unsing the format processor of perl.

So I have a format like

I have a Python 3 app on Google App Engine Standard.

I was using request.remote_addr to get users' IP addresses and it was always returning 127.0.0.1.

I then added werkzeug ProxyFix like this:

We operate a NDBCluster Version 8 and want to replicate a database in this cluster into a "standalone" InnoDB Database System. I followed this guide to implement the replication: http://johanandersson.blogspot.com/2012/09/mysql-cluster-to-innodb-replication.html but it seems, I have done something wrong and I don't know, how to debug it. I know the guide is very old, but I also read the chapter about the NDB Replication on MySQL https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication.html

Current behavior

The replication I set up by now replicates every statement like "Create Database" or "Create Table", even "INSERT" and "UPDATE" statements, as long as the NDBCLUSTER as Engine is not involved. I.e.: I can create a new Database in the cluster and it will be perfectly replicated to the slave. I can insert new datarows to a InnoDB table that I created on the cluster (I know, it is not actually saved in the cluster) and those data rows will be replicated to the slave. Inserting new data rows to a NDBCLUSTER table will result in no replication at all. If I execute the statement "SHOW MASTER STATUS" on the SQL Node in the Cluster before the insert to a NDBCLUSTER table and afterwords, I can see, that the Binlog Position has not changed at all.

Wanted behavior

I want the Replication to replicate data from tables with the NDBCLUSTER Engine to my Slave, that runs on InnoDB. I know there are limitations and we have to be carefull how to structure tables, that everything is compatible, etc.

Current Setup

We operate a MySQL NDB Cluster with 2 Management Nodes, 2 SQL Nodes and 4 Data Nodes and we want to replicate to one InnoDB Server

All Systems have Version 8 installed, run on Ubuntu 18.04 and all Systems have the Cluster Version of the MySQL Server installed. On of the SQL Nodes is chosen to do the replication. The config (/etc/my.cnf) of the Slave in the mysqld section is:

The google-cloud-ndb Python library provides two ways of generating identifiers for Datastore entities:

• integer_id(): Returns the ID as an integer.
• urlsafe(): Returns a base64 string of the key.

If I am creating a URL mapping to a specific entity (eg: /users//) can I use either of these ID options?

I assume there is some benefit to using the base64 encoded version for URLs? The only issue is it results in some pretty ugly URLs, so I prefer to use the integer for aesthetics.

Is there a technical benefit (like improved performance) to using either option?

I have feature with multiple scenarios that are building upon each other. Think of it as the first request fetches some data which is then pumped into the second one and so on.

This works fine, as long as all the requests go to the same host. However the last request in the line goes to a different port on the same host, but of course the port which is called from Karate is the wrong one.

Here the the karate-config.js:

• I want to test the performance of my NDB cluster.
• I am thinking of using sysbench.
• Are there any particular configuration changes required to make it work with the NDB cluster?
• Is there any flag that I need to use during runtime to mention the Storage engine explicitly.

Need some help on this.

For Python 2 GAE, remote_api_shell.py was super handy for making updates to live datastore.

With Python 3 GAE and cloud ndb, this doesn't work. Is there a good replacement?