[CONTROLLER-1984] Remove obsolete datastore.cfg properties Created: 01/Jul/21  Updated: 01/Jul/21  Resolved: 01/Jul/21

Status: Resolved
Project: controller
Component/s: clustering
Affects Version/s: None
Fix Version/s: 4.0.0

Type: Task Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

We have the following entries present:

# The maximum thread pool size for each shard's data store data change notification executor.
# THIS SETTING HAS HAD NO EFFECT FOR A LONG TIME, IS DEPRECATED, AND WILL BE REMOVED IN A FUTURE RELEASE
#max-shard-data-change-executor-pool-size=20

# The maximum queue size for each shard's data store data change notification executor.
# THIS SETTING HAS HAD NO EFFECT FOR A LONG TIME, IS DEPRECATED, AND WILL E REMOVED IN A FUTURE RELEASE
#max-shard-data-change-executor-queue-size=1000

# The maximum queue size for each shard's data store data change listener.
# THIS SETTING HAS HAD NO EFFECT FOR A LONG TIME, IS DEPRECATED, AND WILL BE REMOVED IN A FUTURE RELEASE
#max-shard-data-change-listener-queue-size=1000

# The maximum queue size for each shard's data store executor.
# THIS SETTING HAS HAD NO EFFECT FOR A LONG TIME, IS DEPRECATED, AND WILL BE REMOVED IN A FUTURE RELEASE
#max-shard-data-store-executor-queue-size=5000


Remove them and their supporting code.


Generated at Wed Feb 07 19:56:55 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.