Readme
File for IBM® Spectrum
Conductor 2.4.1 Interim Fix 562258
Readme
File for: IBM Spectrum Conductor
Product
Release: 2.4.1
Update
Name: Interim Fix 562258
Fix
ID: sc-2.4.1-build562258-boa
Publication
Date: October 21, 2020
Interim
fix for the SparkCleanup service to clean up old shuffle service logs.
Contents
1.
List of fixes
2.
Download location
3.
Product and components affected
4.
Installation
5.
Uninstallation
6.
List of files
7.
Product notifications
8.
Copyright and trademark information
1.
List
of fixes
APAR:
P103914
2.
Download location
Download
interim fix 562258 from the following location: https://www.ibm.com/eserver/support/fixes/
3.
Product
and components affected
Component
name, Platform, Fix ID:
conductorspark_core, Linux x86_64,
sc-2.4.1-build562258
4.
Installation
Follow
the instructions in this section to download and install this interim fix to
your cluster.
System
requirements
Linux
x86_64
Installation
a)
Log
on to the primary host as the cluster administrator and stop the SparkCleanup
service:
>
egosh user logon -u Admin -x Admin
>
egosh service stop SparkCleanup
b)
On
each of your management hosts, download and extract the following package
to, for example, a /scfixes directory:
conductorsparkcore-2.4.1.0_x86_64_build562258.tar.gz
c)
On
each of your hosts, run the egoinstallfixes command to install the
downloaded package:
>
egoinstallfixes /scfixes/conductorsparkcore-2.4.1.0_x86_64_build562258.tar.gz
Note: Running the egoinstallfixes command
automatically backs up the current binary files to a fix backup directory for
recovery purposes. Do not delete this backup directory; you will need it if you
want to recover the original files. For more information on using this
command, see the egoinstallfixes command reference.
d)
On
each of your hosts, run the pversions command to
verify the installation:
>
pversions -b 562258
e)
Add the following environment variable to the SparkCleanup service profile:
1.
From the cluster
management console, navigate to System & Services > EGO Services >
Service Profiles > Other Services.
2.
Click SparkCleanup
to open
its service prolife.
3.
Navigate to the ego:ActivitySpecification section of the
service profile, and from the Actions list, select Insert “ego:EnvironmentVariable”.
4.
Add this new environment variable:
Name: SERVICE_LOG_RETENTION_IN_MINS
Value:
Any positive integer
Description:
Use this environment variable to specify the time, in minutes, that the
SparkCleanup service will use to determine if a service log file is old enough
to be deleted.
f) From the primary host, start the SparkCleanup service:
>
egosh service start SparkCleanup
5.
Uninstallation
If
required, follow the instructions in this section to uninstall this interim fix
from your cluster.
a)
Log
on to the primary host as the cluster administrator and stop the SparkCleanup
service:
>
egosh user logon -u Admin -x Admin
>
egosh service stop SparkCleanup
b)
On
each host, roll back this interim fix:
>
egoinstallfixes -r 562258
c)
Edit the SparkCleanup service profile to remove the
following environment variable:
SERVICE_LOG_RETENTION_IN_MINS
d)
From the primary host, start the SparkCleanup service:
>
egosh service start SparkCleanup
6.
List
of files
$EGO_TOP/conductorspark/2.4.1/etc/cleanup.py
7.
Product
notifications
To
receive information about product solution and patch updates automatically,
subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/
on the IBM Support website (http://support.ibm.com). You can edit your
subscription settings to choose the types of information you want to get
notification about, for example, security bulletins, fixes, troubleshooting,
and product enhancements or documentation changes.
8.
Copyright
and trademark information
©
Copyright IBM Corporation 2020
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.