2

During a publish cycle one of my data-centres is eventually failing transactions indicating they are not deployed.

Publishing a couple of hundred items is OK. When I push in a few hundred (I want around 200 thousand eventually!) then the success stops to increment and all transactions stop in waiting for deployment until they eventually timeout.

Finer details:

  • I'm using the MIRROR strategy in deployment.
  • Mirror_1 is a simple master and single worker
  • Mirror_2 is an AWS Load-balancer endpoint
  • The AWS load balancer points to two masters, with two workers

Now - and this may be very related: I did have to move a Finalize="true" from the deployer config as I had the error noted below:

enter image description here

This strikes me as very odd given the XSD would appear to support it:

enter image description here

QUESTION: Why can I not include the Finalize="true" attribute?

Improve this question

1 Answer 1

Reset to default
2

The XSD was updated where the second complexType above (PipelinesType) was actually PipelineType which conflicted from the first.

We have no record of it being updated but it was. Having changed it (or re-copied the install version over it) and restarting the services we thought it would have been up to speed.

Seems a Linux reboot did the trick!

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.