Can you share the code of your extension (also privately) ?
Michael
Am 21.01.2014 um 13:30 schrieb Ramesh Yakkala :
> Hi Michael,
>
> Could you please clear the error messages in the given post,since it have the
> my project package.
>
> Thanks,
> Ramesh Yakkala.
>
> On Tuesday, January 21,
Hi Michael,
Could you please clear the error messages in the given post,since it have
the my project package.
Thanks,
Ramesh Yakkala.
On Tuesday, January 21, 2014 4:38:23 PM UTC+5:30, Michael Hunger wrote:
>
> We don't recommend to run write transaction on the slaves just on the
> master.
> As
#1
You could configure your load balancer to use the available endpoints for
testing which is the master and routing write requests to it. (general docs.
http://docs.neo4j.org/chunked/milestone/ha.html)
concrete docs for the endpoint:
http://docs.neo4j.org/chunked/milestone/ha-rest-info.html
Se
Hi Michael,
May I know how to configure the master could take write operations and
slave should to read operations.
Thanks,
Ramesh Yakkala.
On Tuesday, January 21, 2014 4:38:23 PM UTC+5:30, Michael Hunger wrote:
>
> We don't recommend to run write transaction on the slaves just on the
> master
Hi Michael,
May I know how to configure the master could take write operations and
slave should to read operations.
Thanks,
Ramesh Yakkala.
On Tue, Jan 21, 2014 at 4:38 PM, Michael Hunger <
michael.hun...@neopersistence.com> wrote:
> We don't recommend to run write transaction on the slaves ju
We don't recommend to run write transaction on the slaves just on the master.
As each transaction on the slave will grab a global cluster lock to sync the tx
with the master and only after the master tx commits the slave tx also commits.
Rather write on the master and use push_factor and pull_int
