Thanks Scott for your feedback,
in line
Le 07/05/2015 09:59, Scott Gray a écrit :
I've seen it done with a separate Delegator but it needed a code change
since there's no configurable way to disable the JobManager.
Sure, I found a easier solution on my case. I just changed the ofbiz
instance name on the read only instance to be sure that the jobSandbox
don't try to execute some job.
But a better way would be configure it through the service engine
configuration.
Main issues to be aware of:
- Transaction isolation, you can't see uncommitted modifications made in
same call chain
Exactly
- If the read replica lags too far behind then you have issues if the code
depends on the data being up to date
Mainly, I use this configuration only for the reporting, so we can't
wait 30 seconds. For other case sys admin are available for that ;)
I open a jira issue to follow all ideas :
https://issues.apache.org/jira/browse/OFBIZ-6401
Nicolas
Regards
Scott
On 7 May 2015 08:01, "Nicolas Malin" <[email protected]> wrote:
Hello,
For a customer site I deployed an OFBiz instance connected with a readonly
postgres database (replicated slave).
To realize it, I created a new DAO implementation with only authorize the
find and with some little entity engine configuration (disable eeca), this
work pretty fine.
Do you realized an equivalent OFBiz deployment on read only database ? and
How did you do ? I will appreciate some other feedback to check If my
improvement toke the good ways and if it's interesting to contribute it on
the project (code and wiki ;) ).
Nicolas
