Does Context Store require runtime configuration changes?

Last Updated : Jun 28, 2018 |

Some aspects of Context Store configuration can be changed dynamically, but not all. See lists below for details.

Changes requiring cluster restart

  • Data-grid sizing is not dynamic (ContextStoreManager "Startup Configuration" attributes); you must shut down all the nodes and start the nodes simultaneously if you make changes to the data-grid.

  • The Context Store cluster does not support scaling out dynamically. After adding or removing a node to the cluster, you must shut down all the nodes and start the nodes simultaneously.

Changes requiring service reinstall

  • ContextStoreQuery - reinstall this service after attributes changes.

Changes requiring that the feature is toggled off and on again

  • ContextStoreManager "External Data Mart Configuration" attributes - enable/disable the EDM feature(s) to make configuration changes.

  • ContextStoreManager "Geo Redundancy Configuration" attributes - enable/disable the GEO feature to make configuration changes.

  • ContextStoreNotify - to make changes to the configuration of a subscription, you must first disable the subscription, make the changes, and then enable the subscription again.

Changes that do not require any action other than the change in attribute value itself

  • ContextStoreManager "Run-time Service Configuration"

  • ContextStoreManager "Streams Configuration"

  • ContextStoreRest "External Data Mart Configuration"

  • ContextStoreRest "Advanced Configuration"

  • "Enable Centralized Logging" for any service