Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -1779,6 +1779,21 @@
</description>
</property>

<property>
<name>dfs.datanode.synconclose</name>
<value>false</value>
<description>
If this configuration is enabled, the datanode will instruct the

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If this configuration is enabled, the datanode will instruct the
If this property is enabled, the datanode will instruct the

operating system to sync data block files contents to disk when the
blockfile is closed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
blockfile is closed.
blockfile is closed. This can help data loss in the event of a malfunction such as a power
failure.


This has the benefit of ensuring that data is written to disk
immediately when a block is closed, avoiding the data being held
in the operating system cache. This can help data loss in the event
of a malfunction such as a power failure.
Comment on lines +1790 to +1793

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

..., avoiding the data being held in the operating system cache.

Does the sync of the dirty block in the page cache force the removal of the block from the page cache? I'm not sure that it does. The user can advise the OS, where supported, that it doesn't need the block in the page cache through the dfs.datanode.drop.cache.behind.writes property or related flags when opening the file.

</description>
</property>

<property>
<name>dfs.client.failover.max.attempts</name>
<value>15</value>
Expand Down