Skip to main content

HazelcastClusterConnector

Connects distributed crawler nodes using Hazelcast.

Notesโ€‹

Connects crawler nodes using Hazelcast for distributed crawling. Supports cluster naming, instance naming, node expiry timeout, and worker heartbeat configuration.

Usageโ€‹

class: HazelcastClusterConnector
clusterName: string
configurer:
class: JdbcHazelcastConfigurer
autoDiscoveryEnabled: false
backupCount: 0
columnKeyType: string
columnValueType: string
hazelcastProperties: {}
initialLoadMode: LAZY
jdbcDriver: string
jdbcPassword: string
jdbcUrl: string
jdbcUsername: string
jetEnabled: false
maxPoolSize: 0
queueStoreEnabled: false
sqlMerge: string
tcpMembers: string
writeBatchSize: 0
writeCoalescing: false
writeDelaySeconds: 0
instanceName: string
nodeExpiryTimeout: 0
workerHeartbeatInterval: 0

Propertiesโ€‹

PropertyTypeRequiredDefault
clusterNamestringNocrawler-cluster
configurerHazelcastConfigurerNoJdbcHazelcastConfigurer
instanceNamestringNo-
nodeExpiryTimeoutintegerNo30000
workerHeartbeatIntervalintegerNo1000

Property Detailsโ€‹

clusterNameโ€‹

The name identifying the Hazelcast cluster. All nodes sharing the same cluster name will automatically join the same cluster. Default is "crawler-cluster".

configurerโ€‹

The configurer responsible for building the Hazelcast configuration. Defaults to JdbcHazelcastConfigurer, which uses JDBC persistence with an embedded H2 database in standalone mode. Advanced users can provide a custom HazelcastConfigurer implementation.

instanceNameโ€‹

Name of the Hazelcast instance to use for this cluster connector.

nodeExpiryTimeoutโ€‹

The maximum time to wait before declaring a node as expired in a distributed crawl. Minimum effective value is 5 seconds. Default is 30 seconds. Not applicable in standalone mode.

workerHeartbeatIntervalโ€‹

How frequently (in milliseconds) a worker signals that it is still alive. Used to detect stalled or crashed workers.