Rashmi, Does this mean that if the job does not finish within a specified period, it should be terminated?
It's useful to remember that Corb is not doing one big transaction; it is serializing a bunch of small transactions to accomplish some goal. With that in mind, if the overall Corb process were terminated because it took too long, it would not roll back the transactions that it had completed. Corb runs a particular module on a series of URIs; if your goal is to make sure that the module doesn't spend too much time on one particular URI, you can limit the default time limit of the XDBC app server. Suppose you set that to 30 seconds; then any URI that required more than 30 seconds of processing would fail, thus achieving an upper limit on a per-document basis. Note that you'd be left with some documents successfully updated (those that took < 30 seconds) and some that failed (those that took > 30 seconds). Dave. -- Dave Cassel Developer Community Manager MarkLogic Corporation<http://www.marklogic.com/> Cell: +1-484-798-8720 From: Rashmi Ranjan Acharya <[email protected]<mailto:[email protected]>> Reply-To: MarkLogic Developer Discussion <[email protected]<mailto:[email protected]>> Date: Tuesday, November 4, 2014 at 6:13 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [MarkLogic Dev General] Executing CORB with a time limit Hi All, Is there any way to run a CORB with a particular time limit? I am executing CORB through shell script with Java class path. Thanks in advance!!! Rashmi Ranjan Acharya TATA Consultancy Services, Kolkata, India Cell:+91-9874844188 _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
