Interface HibernateSearchOutboxPollingRuntimeConfigPersistenceUnit.MassIndexerConfig

Enclosing interface:
HibernateSearchOutboxPollingRuntimeConfigPersistenceUnit

public static interface HibernateSearchOutboxPollingRuntimeConfigPersistenceUnit.MassIndexerConfig
  • Method Summary

    Modifier and Type
    Method
    Description
    How long to wait for another query to the agent table when actively waiting for event processors to suspend themselves.
    How long an event processor "pulse" remains valid before considering the processor disconnected and forcibly removing it from the cluster.
    How long the mass indexer can wait before it must perform a "pulse", updating and checking registrations in the agent table.
  • Method Details

    • pollingInterval

      @WithDefault("0.100S") Duration pollingInterval()
      How long to wait for another query to the agent table when actively waiting for event processors to suspend themselves. Low values will reduce the time it takes for the mass indexer agent to detect that event processors finally suspended themselves, but will increase the stress on the database while the mass indexer agent is actively waiting. High values will increase the time it takes for the mass indexer agent to detect that event processors finally suspended themselves, but will reduce the stress on the database while the mass indexer agent is actively waiting. See link:{hibernate-search-docs-url}#coordination-outbox-polling-mass-indexer[this section of the reference documentation] for more information.
    • pulseInterval

      @WithDefault("2S") Duration pulseInterval()
      How long the mass indexer can wait before it must perform a "pulse", updating and checking registrations in the agent table. The pulse interval must be set to a value between the polling interval and one third (1/3) of the expiration interval. Low values (closer to the polling interval) mean reduced risk of event processors starting to process events again during mass indexing because a mass indexer agent is incorrectly considered disconnected, but more stress on the database because of more frequent updates of the mass indexer agent's entry in the agent table. High values (closer to the expiration interval) mean increased risk of event processors starting to process events again during mass indexing because a mass indexer agent is incorrectly considered disconnected, but less stress on the database because of less frequent updates of the mass indexer agent's entry in the agent table. See link:{hibernate-search-docs-url}#coordination-outbox-polling-mass-indexer[this section of the reference documentation] for more information.
    • pulseExpiration

      @WithDefault("30S") Duration pulseExpiration()
      How long an event processor "pulse" remains valid before considering the processor disconnected and forcibly removing it from the cluster. The expiration interval must be set to a value at least 3 times larger than the pulse interval. Low values (closer to the pulse interval) mean less time wasted with event processors not processing events when a mass indexer agent terminates due to a crash, but increased risk of event processors starting to process events again during mass indexing because a mass indexer agent is incorrectly considered disconnected. High values (much larger than the pulse interval) mean more time wasted with event processors not processing events when a mass indexer agent terminates due to a crash, but reduced risk of event processors starting to process events again during mass indexing because a mass indexer agent is incorrectly considered disconnected. See link:{hibernate-search-docs-url}#coordination-outbox-polling-mass-indexer[this section of the reference documentation] for more information.