Table data not reflected in read data store after update in write data store

[thiruopti]

Node version: 12.x Sails version (sails):1.0.x ORM hook version (sails-hook-orm): 3.1.0 DB adapter & version (e.g. sails-mysql@5.55.5): sails-mysql@1.0.1 Skipper adapter & version (e.g. skipper-s3@5.55.5): skipper-s3@0.6.0

---

We using two data stores for database operations. One connection is used for reading data from read database. Another one used for Create/Update/Delete mysql operations. What's the issue we faced is we can't able to get updated data in read data store immediately after certain time periods or request calls. We have to restart the sails app in order to get latest data from read data store. Is that anything we missed to configure with multi data store configurations ? Mysql Used : AWS RDS Server: EC2 Instance Sample connection string:

This is the sample connection string we used default: { adapter: 'sails-mysql', user: 'root', password: '', host: 'localhost', // RDS database database: 'test', multipleStatements: true, port: 3306, pool: true, // ssl: true, url: 'mysql://root@localhost:3306/test' }, writeSqlserver: { adapter: 'sails-mysql', user: 'root', password: '', host: 'localhost', // RDS database database: 'test', multipleStatements: true, port: 3306, pool: true, // ssl: true, url: 'mysql://root@localhost:3306/test },

Sample Find query: await Users.findOne({userId:1})

[sailsbot]

@thiruopti Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

  ---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.

[eashaw]

Hi @thiruopti, We were looking at this issue and we had some questions about your use case. We understand why you have two databases but why do you have two datastores in your config? Would you be able to create a minimal Sails repo that recreates this issue so we can further examine it?