Bug 1139458

Summary:	add to the installer rhs-high-throughput profile, on each storage node
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jeff Vance <jvance>
Component:	rhs-hadoop-install	Assignee:	Jeff Vance <jvance>
Status:	CLOSED ERRATA	QA Contact:	Jakub Rumanovsky <jrumanov>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	bchilds, dahorak, divya, eboyd, jrumanov, jvance, matt, mkudlej, mvecera, nlevinki, screeley
Target Milestone:	Release Candidate	Keywords:	Triaged, UpcomingRelease, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.17-1	Doc Type:	Bug Fix
Doc Text:	Previously, the rhs-high-thoughput profile was not enabled by the setup_cluster.sh script. Now, with this release, --profile allows enabling rhs-high-thoughput profile by setup_cluster.sh script.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-24 11:55:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1159155

Description Jeff Vance 2014-09-09 01:48:37 UTC

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Better hadoop performance will result if the rhs-high-throughput tuned-adm profile is set up on each storage node in the cluster

Steps to Reproduce:
1. run post Denali version of installer
2. tuned-adm active
3. see the deault profile is active

Actual results:


Expected results:


Additional info:

Comment 2 Jeff Vance 2014-09-09 01:54:39 UTC

fixed in 2.15

Comment 3 Jeff Vance 2014-09-12 18:38:28 UTC

Version 2.17 of setup_cluster.sh supports a new --profile option. The default is to not change the tuned-adm profile. But, if --profile <profileName> is specified then that profile is verified and set.

Comment 4 Jakub Rumanovsky 2014-10-27 09:15:53 UTC

I tested it on 2x2, 2x2 with mgmt and brick on the same node and 1x2 with mgmt and brick on the same node.

It does not work with the last mentioned layout (the machine with brick and mgmt on the same node stays on default profile), but Im not sure it applies on 1x2 scenarios, but Im writing it here just to be sure.

On the other scenarios, it works well (all the nodes are switched to rhs-high-throughput after running ./setup_cluster with --profile option).

Please, write, if it apply on 1x2 scenarios also

Thank you
Jakub Rumanovsky

Comment 10 Jakub Rumanovsky 2014-11-12 14:21:55 UTC

see also BUG 1150069 COMMENT 11 for clarification about RHS packages removal

Comment 11 Divya 2014-11-14 08:27:21 UTC

Jeff,

Could you please provide the doc text in the Doc Text field for this bug?

Comment 12 Divya 2014-11-21 08:24:16 UTC

Jeff,

Could you please review the edited doc text for technical accuracy and sign-off?

Comment 14 errata-xmlrpc 2014-11-24 11:55:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2014-1275.html