[HDDS-11405] Ambiguous behaviour of the ozone fs -setrep command

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Ozone CLI
• Labels: pull-request-available
• Assignee: Sadanand Shenoy
• Reporter: Karn Kumar Singh
• Created: 03/Sep/24 08:03
• Updated: 19/Nov/24 14:09

Description

Repro step: 

1. Create a key of any size(including 0 bytes).
2. Set the replication using the 'ozone fs -setrep' command with a replication factor other than the default.

Log:

# ozone fs -setrep -w 5 ofs://ozone1/voltmp/buck
Replication 5 set: ofs://ozone1/voltmp/buck/key
Waiting for ofs://ozone1/voltmp/buck/key ... done
# ozone fs -stat '%r' ofs://ozone1/voltmp/buck
1
# ozone fs -stat '%r' ofs://ozone1/voltmp/buck/key
3

The command gets executed instantly for the 0-byte key, but the command is stuck forever for the non-0-byte key.

Log: 

# ozone fs -du ofs://ozone1/voltmp/buck
0     0      ofs://ozone1/voltmp/buck/key
7190  21570  ofs://ozone1/voltmp/buck/key1
# ozone fs -setrep -w 5 ofs://ozone1/voltmp/buck
Replication 5 set: ofs://ozone1/voltmp/buck/key
Replication 5 set: ofs://ozone1/voltmp/buck/key1
Waiting for ofs://ozone1/voltmp/buck/key ... done
Waiting for ofs://ozone1/voltmp/buck/key1 .........................

Issue Links

• links to: GitHub Pull Request #7164