EntitySync modifying defaultSyncEndBufferMillis ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

EntitySync modifying defaultSyncEndBufferMillis ?

oceatoon
Hi ofbizians

We needed to be able to modify and instantly sync data between two Ofbiz
instances
to do this we changed the defaultSyncEndBufferMillis of the EntitySync files
from 300000 to 1000.
It seems to work , I just wanted to make sure with someones experienced view
on why would this be at 5min in the first place, and
if bringing it down to 1s could cause problems?

Thanks for the thoughts
Best Regards
Tibor
Reply | Threaded
Open this post in threaded view
|

Re: EntitySync modifying defaultSyncEndBufferMillis ?

David E Jones-2

The main reason for this is that if there are multiple application  
servers hitting a database their clocks may not be 100% in sync. This  
waiting five minutes allows the clocks to be up to five minutes out  
of sync without one server overstepping the time on the other and  
leaving data in that dead-zone not sent to the other server, with no  
good way of knowing that it wasn't sent.

If you have a single app server hitting the database, it should be  
okay to use a pretty small time. One second might be a little bit too  
small because you may have outstanding short-lived transactions that  
have not completed and that might be missed...

-David


On Oct 19, 2006, at 3:50 AM, tibor katelbach wrote:

> Hi ofbizians
>
> We needed to be able to modify and instantly sync data between two  
> Ofbiz
> instances
> to do this we changed the defaultSyncEndBufferMillis of the  
> EntitySync files
> from 300000 to 1000.
> It seems to work , I just wanted to make sure with someones  
> experienced view
> on why would this be at 5min in the first place, and
> if bringing it down to 1s could cause problems?
>
> Thanks for the thoughts
> Best Regards
> Tibor

Reply | Threaded
Open this post in threaded view
|

Re: EntitySync modifying defaultSyncEndBufferMillis ?

oceatoon
Thanks a lot David.


On 10/19/06, David E Jones <[hidden email]> wrote:

>
>
> The main reason for this is that if there are multiple application
> servers hitting a database their clocks may not be 100% in sync. This
> waiting five minutes allows the clocks to be up to five minutes out
> of sync without one server overstepping the time on the other and
> leaving data in that dead-zone not sent to the other server, with no
> good way of knowing that it wasn't sent.
>
> If you have a single app server hitting the database, it should be
> okay to use a pretty small time. One second might be a little bit too
> small because you may have outstanding short-lived transactions that
> have not completed and that might be missed...
>
> -David
>
>
> On Oct 19, 2006, at 3:50 AM, tibor katelbach wrote:
>
> > Hi ofbizians
> >
> > We needed to be able to modify and instantly sync data between two
> > Ofbiz
> > instances
> > to do this we changed the defaultSyncEndBufferMillis of the
> > EntitySync files
> > from 300000 to 1000.
> > It seems to work , I just wanted to make sure with someones
> > experienced view
> > on why would this be at 5min in the first place, and
> > if bringing it down to 1s could cause problems?
> >
> > Thanks for the thoughts
> > Best Regards
> > Tibor
>
>