[jira] [Created] (HDFS-15283) Cache pool MAXTTL is not persisted and restored on cluster restart

["Stephen O'Donnell (Jira)" <ji...@apache.org>]

Stephen O'Donnell created HDFS-15283:
----------------------------------------

             Summary: Cache pool MAXTTL is not persisted and restored on cluster restart
                 Key: HDFS-15283
                 URL: https://issues.apache.org/jira/browse/HDFS-15283
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 3.4.0
            Reporter: Stephen O'Donnell
            Assignee: Stephen O'Donnell


The cache pool "getMaxRelativeExpiryMs" is never persisted to or read from the FSImage. This means that if a MAXTTL is set on a pool, it will not persist beyond a cluster restart.

From the protobuf definition, there is an existing field to store it:

{code}
message CachePoolInfoProto {
  optional string poolName = 1;
  optional string ownerName = 2;
  optional string groupName = 3;
  optional int32 mode = 4;
  optional int64 limit = 5;
  optional int64 maxRelativeExpiry = 6; <-- NEVER SET
  optional uint32 defaultReplication = 7 [default=1];
}
{code}

But this is never set in the CacheManager.saveState() or read in CacheManager.loadState().



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org