Cache size used in named should be configurable
Bug #1493957 reported by
Hari Prasad Killi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.0 |
Fix Committed
|
Medium
|
Hari Prasad Killi | |||
R2.20 |
Fix Committed
|
Medium
|
Hari Prasad Killi | |||
Trunk |
Fix Committed
|
Medium
|
Hari Prasad Killi |
Bug Description
Max cache size used by named should be configurable via contrail-dns config file.
This value will be used for the following:
max-cache-size defines the maximum amount of memory to use for the server's cache, in bytes (case insensitive shortforms of k or m are allowed). When the amount of data in the cache reaches this limit, the server will cause records to expire prematurely so that the limit is not exceeded. In a server with multiple views, the limit applies separately to the cache of each view. The default is unlimited, meaning that records are purged from the cache only when their TTLs expire. This statement may be used in view or a global options clause.
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/13718
Submitter: Hari Prasad Killi (<email address hidden>)