Bug 1241160 - document fs.glusterfs.sort.directory.listing property of rhs-hadoop plugin
Summary: document fs.glusterfs.sort.directory.listing property of rhs-hadoop plugin
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Installation_Guide
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Anjana Suparna Sriram
QA Contact: BigData QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-08 15:31 UTC by Martin Bukatovic
Modified: 2018-04-09 11:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
team-cce
Clone Of:
Environment:
Last Closed: 2018-04-09 11:49:40 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1093838 0 medium CLOSED Brick-sorted order of filenames in RHS directory harms Hadoop mapreduce performance 2023-09-14 02:07:17 UTC

Internal Links: 1093838

Description Martin Bukatovic 2015-07-08 15:31:04 UTC
Document URL
============

Red Hat Storage 3: Installation Guide

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html-single/Installation_Guide/index.html#chap-Deploying_the_Hortonworks_Data_Platform_2.1_on_Red_Hat_Storage

Section Number and Name
=======================

Chapter 8. Deploying the Hortonworks Data Platform 2.1 on Red Hat Storage

Describe the issue
==================

BZ 1093838 introduced new feature which can be enabled via new configuration
property of rhs-hadoop plugin: fs.glusterfs.sort.directory.listing

This feature is disabled by default, but since it can be useful it needs to be
documented so that admin of rhs-hadoop cluster can decide if and how to enable
it.

Suggestions for improvement
===========================

Refer to comment 2 and 3 of BZ 1093838 for details and reasoning behind this
feature.

I'm not sure where to put it inside the Chapter. Also feel free to reassign
this to Administration Guide instead if you find this solution more
appropriate.


Note You need to log in before you can comment on or make changes to this bug.