On Oct 24, 2017, at 9:02 AM, Daniele Mantovani <dmantovani@salesianisesto.it> wrote:
I'm looking at the decoupled-accounting and if I've understood well, it's a sort of pipe: You send the accounting to a detail log file, then a virtual server read that detail log file and send that to the sql.
Yes.
This method is suggested even on the master server? (So the accounting virtual server end the request in less time, and then the sql insert is done in another virtual server)
The master can write directly to SQL.
One thing that I don't see is how it work in case of the sql server is not working: Does it use a sort of pointer/position, to read the data from the detail log, like the mysql binary log? So if the sql is not available, when it come back online, it start to insert the data from the last un-inserted data? Or is a sort of pipe, and it only try to insert to sql once, when the data is written to the log file?
Read the file. Look for "track progress". This is documented. Alan DeKok.