ayushtkn commented on pull request #3378:
URL: https://github.com/apache/hadoop/pull/3378#issuecomment-912338368


   HDFS-13820, added this configuration to disable the feature, But still it 
was made to true by default, guess due to compatibility reasons.
   Folks using the Cache feature would get impacted with this change, right? 
they have to now enable this explicitly. There was a proposal on on HDFS-13820
   ```
   Please implement a way to disable the CacheReplicationMonitor class if there 
are no paths specified. Adding the first cached path to the NameNode should 
kick off the CacheReplicationMonitor and when the last one is deleted, the 
CacheReplicationMonitor should be disabled again.
   ``` 
   Is something like this possible?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to