I'd be really careful about syncing objects to 1 child server but not other child servers. This can create a giant mess:
if you sync an object to child server A but not to child server B, then imagine that later on the object is edited on child server A. This sends an 'update' message back to the parent, which is processed correctly. But then, the parent sends that 'update' message to all of the other child servers, but sync on the child servers can't process the item as an update because it doesn't exist. At this point you have system-wide sync failures (except for communication between the parent and child server A) until you fix things manually. There are cases in which its OK to block certain openmrs objects from certain child servers using the administration tools -- look at the way GlobalProperties are filtered for an example of this. But, you have to *REALLY* think about what you're doing before getting creative with this feature. d On Wed, Mar 14, 2012 at 6:41 AM, Mark Goodrich <[email protected]> wrote: > Also, if you mark a record as “Not To Sync” I don’t believe it will > “unsync” the record from any child servers it has already synced to.**** > > ** ** > > So, for instance, if you have a record that has synced on Child A, but has > had an error while trying to sync to Child B (and is therefore holding up > the Child B sync queue) you should be able to mark this record as “not to > sync” without worrying about the record being removed from Child A.**** > > ** ** > > Also, you should then be able to mark this record as “Send as new Sync > record”, and, although the record should be sent again to both Child A and > Child B, Child A should be smart enough to realize that it has already > received this record and ignore it, while Child B will attempt to import > the record again.**** > > ** ** > > Mark**** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Ben Wolfe > *Sent:* Wednesday, March 14, 2012 8:47 AM > *To:* [email protected] > *Subject:* Re: [OPENMRS-IMPLEMENTERS] SYNC PARENT SERVER History Changes** > ** > > ** ** > > If you want one specific record to not go to a child server you can delete > that sync_server_record row. I can't remember if there is a way to do this > in the interface. > > If you want one class of object to not go to one of the child servers you > can configure that. On the parent server, edit the "objects not to send" > list to have that object class. OR, on the child server, edit the "objects > to not receive" list to have the object class. The former is a better > option because then you don't waste time/space/bandwidth compiling and > sending the object to the child server only to have the child server deny > it. > > If there is an error in the sync queue at one child server it won't hold > up the other child servers from getting their updates. However, that child > server will continue to get a backlog of objects that will need to be > sync'd. It is a good practice to check the sync queues every morning to > make sure everything has been processed. > > Ben**** > > On Wed, Mar 14, 2012 at 8:04 AM, Erick Mugoma <[email protected]> > wrote:**** > > Looking at history changes ui on parent server, > Is it possible to allow a record to sync on one child server and not on > the other children within the sync network? > > I've noticed that if you mark the record as not for sync on one server it > does not do the same to all the servers. > > So wot happens when one sync record is synced on one server and not able > to be sync on the other children? Looks like it blocks the sync queue so > how do we resolve this problem? > > Thanks > > Erick**** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list > **** > > ** ** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list > **** > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list > _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
