[
  {
    "deprecated_setting": "db.cluster.raft.leader_transfer.priority_group",
    "deprecated_setting_description": "The name of a server_group whose members should be prioritized as leaders. This does not guarantee that the leader will always be a member of this group, but the cluster will attempt to transfer the leadership to such a member when possible. If a database is specified using db.cluster.raft.leader_transfer.priority_group.<database>, the specified priority group will apply to that database only. If no database is specified, that group will be the default and apply to all databases with no explicitly set priority group. Using this setting will disable leadership balancing.",
    "deprecated_version": "Deprecated in 5.4"
  },
  {
    "deprecated_setting": "dbms.cluster.discovery.endpoints",
    "deprecated_setting_description": "A comma-separated list of endpoints that a server should contact in order to discover other cluster members.\nTypically, all cluster members, including the current server, must be specified in this list.\nThe setting configures the endpoints for Discovery service V1.",
    "deprecated_version": "Deprecated in 5.23"
  },
  {
    "deprecated_setting": "dbms.cluster.discovery.log_level",
    "deprecated_setting_description": "The level of middleware logging.",
    "deprecated_version": "Deprecated in 5.23"
  },
  {
    "deprecated_setting": "dbms.cluster.discovery.type",
    "deprecated_setting_description": "This setting has been replaced by dbms.cluster.discovery.resolver_type.",
    "deprecated_version": "Deprecated in 5.7"
  },
  {
    "deprecated_setting": "dbms.cluster.discovery.version",
    "deprecated_setting_description": "This setting allows you to select which discovery service should be started.\nPossible values are:\n* V1_ONLY\u2009\u2014\u2009it runs only discovery service v1.\n* V1_OVER_V2\u2009\u2014\u2009it runs both Discovery Service V1 and Discovery Service V2, where V1 is the main service and V2 runs in the background.\n* V2_OVER_V1\u2009\u2014\u2009it runs both Discovery Service V1 and Discovery Service V2, where V2 is the main service and V1 runs in the background.\n* V2_ONLY\u2009\u2014\u2009it runs only discovery service v2.",
    "deprecated_version": "Deprecated in 5.26"
  },
  {
    "deprecated_setting": "initial.dbms.database_allocator",
    "deprecated_setting_description": "Name of the initial database allocator. After the creation of the DBMS, it can be set by running the CALL dbms.setDatabaseAllocator() procedure.",
    "deprecated_version": "Deprecated in 5.23"
  },
  {
    "deprecated_setting": "server.cluster.catchup.connect_randomly_to_server_group",
    "deprecated_setting_description": "Comma-separated list of groups to be used by the connect-randomly-to-server-group selection strategy. The connect-randomly-to-server-group strategy is used when the list of strategies (server.cluster.catchup.upstream_strategy) includes the value connect-randomly-to-server-group.",
    "deprecated_version": "Deprecated in 5.4"
  },
  {
    "deprecated_setting": "server.discovery.listen_address",
    "deprecated_setting_description": "Host and port to bind the cluster member discovery management communication.",
    "deprecated_version": "Deprecated in 5.23"
  },
  {
    "deprecated_setting": "server.groups",
    "deprecated_setting_description": "A list of tag names for the server used when configuring load balancing and replication policies.",
    "deprecated_version": "Deprecated in 5.4"
  },
  {
    "deprecated_setting": "server.discovery.advertised_address",
    "deprecated_setting_description": "Advertised cluster member discovery management communication.",
    "deprecated_version": "Deprecated in 5.23"
  },
  {
    "deprecated_setting": "dbms.cluster.catchup.client_inactivity_timeout",
    "deprecated_setting_description": "The catch-up protocol times out if the given duration elapses with no network activity. Every message received by the client from the server extends the timeout duration.",
    "deprecated_version": "Deprecated in 5.26"
  },
  {
    "deprecated_setting": "db.logs.query.annotation_data_as_json_enabled",
    "deprecated_setting_description": "Log the annotation data as JSON strings instead of a Cypher map. This configuration has an effect only when the query log is in JSON format.\nFrom 5.9, if true, it collapses the nested JSON objects in the query logger.",
    "deprecated_version": "Deprecated in 5.12"
  },
  {
    "deprecated_setting": "db.tx_state.memory_allocation",
    "deprecated_setting_description": "Defines whether memory for transaction state should be allocated on- or off-heap. Note that for small transactions you can gain up to 25% write speed by setting it to ON_HEAP.",
    "deprecated_version": "Deprecated in 5.8"
  },
  {
    "deprecated_setting": "server.db.query_cache_size",
    "deprecated_setting_description": "The number of cached Cypher query execution plans per database. The max number of query plans that can be kept in cache is the number of databases * server.db.query_cache_size. With 10 databases and server.db.query_cache_size=1000, the caches can keep 10000 plans in total on the instance, assuming that each DB receives queries that fill up its cache.",
    "deprecated_version": "Deprecated in 5.7"
  },
  {
    "deprecated_setting": "server.memory.off_heap.transaction_max_size",
    "deprecated_setting_description": "The maximum amount of off-heap memory that can be used to store transaction state data; it\u2019s a total amount of memory shared across all active transactions. Zero means 'unlimited'. Used when db.tx_state.memory_allocation is set to 'OFF_HEAP'.",
    "deprecated_version": "Deprecated in 5.8"
  },
  {
    "deprecated_setting": "server.memory.off_heap.block_cache_size",
    "deprecated_setting_description": "Defines the size of the off-heap memory blocks cache. The cache will contain this number of blocks for each block size that is power of two. Thus, maximum amount of memory used by blocks cache can be calculated as 2 server.memory.off_heap.max_cacheable_block_size",
    "deprecated_version": "Deprecated in 5.26"
  },
  {
    "deprecated_setting": "server.memory.off_heap.max_cacheable_block_size",
    "deprecated_setting_description": "Defines the maximum size of an off-heap memory block that can be cached to speed up allocations. The value must be a power of 2.",
    "deprecated_version": "Deprecated in 5.26"
  },
  {
    "deprecated_setting": "dbms.kubernetes.service_port_name",
    "deprecated_setting_description": "Service port name for discovery for Kubernetes API.",
    "deprecated_version": "Deprecated in 5.23"
  },
  {
    "deprecated_setting": "server.max_databases",
    "deprecated_setting_description": "The maximum number of databases.",
    "deprecated_version": "Deprecated in 5.6"
  }
]