com.atlassian.confluence.event.events.cluster

Interface ClusterEvent

All Known Implementing Classes:

AsyncImportFinishedEvent, ClusterAccessModeEvent, ClusterCacheFlushEvent, ClusterDisableJobEvent, ClusterEnableJobEvent, ClusterIndexRequestEvent, ClusterIndexResponseEvent, ClusterIndexSnapshotCreatedEvent, ClusterIndexSnapshotRequestEvent, ClusterIndexSnapshotRequestReceivedEvent, ClusterMaintenanceBannerEvent, ClusterPanicEvent, ClusterReindexRequiredEvent, ClusterSharedHomeSanityCheckEvent, ClusterUpdateCronJobScheduleEvent, ClusterUpdateSimpleJobScheduleEvent, CollaborativeEditingOffEvent, CollaborativeEditingOnEvent, ConfluenceDirectoryEventListener.ClusterDirectoryDeletedEvent, ConfluenceDirectoryEventListener.ClusterDirectoryEvent, ConfluenceDirectoryEventListener.ClusterDirectoryUpdatedEvent, DefaultIndexFlushRequester.RequestIndexFlushEvent, GlobalSettingsChangedEvent, ImportFinishedEvent, MailServerCreateEvent, MailServerDeleteEvent, MailServerEditEvent, MailServerEvent, MaxCacheSizeChangedEvent, PauseAllJobsEvent, PauseJobEvent, PauseJobGroupEvent, PluginDisableEvent, PluginEnableEvent, PluginEvent, PluginInstallEvent, PluginModuleDisableEvent, PluginModuleEnableEvent, PluginModuleEvent, PluginUninstallEvent, ResetHibernateIdRangeEvent, ResumeJobEvent, SiteDarkFeatureDisabledEvent, SiteDarkFeatureEnabledEvent

public interface ClusterEvent

Marker interface for those events which should be broadcast to other nodes in a cluster.

Broadcast events should be used sparingly, as they will have a major impact on performance of a cluster. Where possible, use Bandana or a clustered cache to store data which should be shared between different nodes, rather than using events to synchronise application state.

The clustered event handler will make sure that events produced within a transaction are not actually sent to the other cluster nodes until the transaction is successfully committed.

See Also:

ClusterManager, ClusterEventBroadcaster, ClusterEventWrapper, BandanaManager, CacheManager