Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can try increasing the 'compass.transaction.lockTimeout' setting. The default is 10 (seconds). </p> <p>Another option is to disable concurrency in Compass and make it synchronous. This is controlled with the 'compass.transaction.processor.read_committed.concurrentOperations': 'false' setting. You might also have to set 'compass.transaction.processor' to 'read_committed'</p> <p>These are the compass settings we are currently using:</p> <pre><code>compassSettings = [ 'compass.engine.optimizer.schedule.period': '300', 'compass.engine.mergeFactor':'1000', 'compass.engine.maxBufferedDocs':'1000', 'compass.engine.ramBufferSize': '128', 'compass.engine.useCompoundFile': 'false', 'compass.transaction.processor': 'read_committed', 'compass.transaction.processor.read_committed.concurrentOperations': 'false', 'compass.transaction.lockTimeout': '30', 'compass.transaction.lockPollInterval': '500', 'compass.transaction.readCommitted.translog.connection': 'ram://' ] </code></pre> <p>This has concurrency switched off. You can make it asynchronous by changing the 'compass.transaction.processor.read_committed.concurrentOperations' setting to 'true'. (or removing the entry).</p> <p>Compass configuration reference: <a href="http://static.compassframework.org/docs/latest/core-configuration.html" rel="nofollow">http://static.compassframework.org/docs/latest/core-configuration.html</a></p> <p>Documentation for the concurrency of read_committed processor: <a href="http://www.compass-project.org/docs/latest/reference/html/core-searchengine.html#core-searchengine-transaction-read_committed" rel="nofollow">http://www.compass-project.org/docs/latest/reference/html/core-searchengine.html#core-searchengine-transaction-read_committed</a></p> <p>If you want to keep async operations, you can also control the number of threads it uses. Using compass.transaction.processor.read_committed.concurrencyLevel=1 setting would allow asynchronous operations but just use one thread (the default is 5 threads). There are also the compass.transaction.processor.read_committed.backlog and compass.transaction.processor.read_committed.addTimeout settings. </p> <p>I hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POSearchable index gets locked on manual update (LockObtainFailedException)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLari Hotari
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSearchable index gets locked on manual update (LockObtainFailedException)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks a lot for the quick reply! We'll try the Compass settings that you suggested. I'll let you know if the problem gets solved after a test period of a few days.
      singulars
      1. PO
      1. USMikko
    2. COWe are doing re-indexing inside a DomainClass.withNewTransaction { .. } block with 1000 entities at a time. Compass follows the same transaction context. In your code it's not clear when the transaction ends. I'd recommend moving logic from a Job to a Service. Your Job class should have "static concurrent = false" and use synchronized methods in the service to prevent concurrent execution instead of some complex locking solution.
      singulars
      1. PO
      1. USLari Hotari
    3. COHi! We moved the indexing logic from quartz job to a synchronized service method and added a withNewTransaction code block around the reindex method call as you suggested. CPU usage is normal now after a test period of one week and there hasn't been any locking issues. Thank you a lot for your help!
      singulars
      1. PO
      1. USMikko
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload