IBM Platform Symphony 6.1.1 Interim Fix 356027 Readme File

Abstract

PMR service logs should auto-rotate.

Description

The MapReduce server logs use 30 GB of space on each data node, and must be deleted manually daily. This fix allows customers to configure PMR service logs to auto-rotate.

This fix applies only to IBM InfoSphere BigInsights 3.0 Linux 64-bit.

Readme file for: IBM® Platform Symphony

Product/Component Release: 6.1.1

Update Name: Interim Fix 356027

Fix ID: sym-6.1.1-build356027

Publication date: 19 August 2015

Last modified date: 19 August 2015

Contents:

1. List of fixes

2. Download location

3. Products or components affected

4. Installation and configuration

5. List of files

6. Copyright and trademark information

1. List of fixes

APAR P101287

2. Download location

Download Fix 356027 from the following location: http://www.ibm.com/eserver/support/fixes/

3. Products or components affected

Product/Component Name:

Platform Symphony/MapReduce

4. Installation and configuration

4.1 Before installation

1. Stop the IBM InfoSphere BigInsights cluster.

> stop-all.sh

2. Back up the file.

Log on to every management and compute host in the cluster and back up the following file that will be replaced by this fix:

> $PMR_HOME/integration/IBM_BigInsights_2.1.2/pmr-hadoop-plus-2.2.0-mr1.jar

4.2 Installation steps

Log on to every management and compute host in the cluster and replace the old file with the downloaded one in the following directory:

> $PMR_HOME/integration/IBM_BigInsights_2.1.2/pmr-hadoop-plus-2.2.0-mr1.jar

4.3 After installation

1. Run the integration script on every management and compute host with root permission.

> $PMR_HOME/integration/IBM_BigInsights_2.1.2/jar_integration.sh

2. Add the section below to log4j.properties in the HADOOP_CONF_DIR folder :

log4j.appender.pmr.service.MaxFileSize=10000KB

log4j.appender.pmr.service.MaxBackupIndex=10

MaxFileSize: the maximum size that the output file is allowed to reach before being rolled over to backup files.

The MaxFileSize option takes an long integer in the range 0 - 2^63.

You can specify the value with the suffixes "KB", "MB" or "GB" so that the integer is interpreted being expressed respectively in kilobytes, megabytes or gigabytes.

For example, the value "10KB" will be interpreted as 10240; The default maximum file size is 10MB.

MaxBackupIndex: the maximum number of backup files to keep around, the MaxBackupIndex option determines how many backup files are kept before the oldest is erased.

This option takes a positive integer value. If set to zero, then there will be no backup files and the log file will be truncated when it reaches MaxFileSize.

There is one backup file by default.

3. Start the cluster.

> start-all.sh

4.4 Uninstallation

1. Stop the cluster.

> stop-all.sh

2. Restore the backup file.

Log on to every management and compute host in the cluster and restore the backup file:

> $PMR_HOME/integration/IBM_BigInsights_2.1.2/pmr-hadoop-plus-2.2.0-mr1.jar

3. Run the integration script on every management and compute host with root permission.

> $PMR_HOME/integration/IBM_BigInsights_2.1.2/jar_integration.sh

4. Start the cluster.

> start-all.sh

5. List of files

pmr-hadoop-plus-2.2.0-mr1.jar

6. Copyright and trademark information

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.