Readme File for IBM^® Spectrum Conductor 2.4.1 Interim Fix 552361

Readme File for: IBM Spectrum Conductor

Product Release: 2.4.1

Update Name: Interim Fix 552361

Fix ID: sc-2.4.1-build552361-boa

Publication Date: July 16, 2020

 

This interim fix provides the following enhancements:

1.      Allow a parallel deployment to all hosts in an instance group while the instance group is in Started or Processing state.

2.      Automatically block hosts from Spark workload (drivers and executors) when they are added to a resource group.

3.      Automatically open hosts after they have been blocked.

4.      Address performance issues with fix 550350.

The following new ascd.conf parameters are introduced in this interim fix:

ASC_ALLOW_DEPLOY_IN_STARTED_STATE

Description: Specifies whether a full redeployment of an application instance or instance group can be performed while the instance group is in Started or Processing state.

Note: When deploying an application instance or instance group to all hosts, all packages associated with the instance will be undeployed and redeployed. The scripts associated with the out-of-box Spark packages are designed to avoid removing files for an instance group host in this case. If you are using this feature with custom application instances or custom service packages within an instance group, ensure the deploy and undeploy scripts for any custom packages also avoid removing files for an instance group host.

Default value: OFF

 

ASC_AUTO_BLOCK_NEW_HOSTS

Description: Specifies whether hosts should be blocked from application instance and instance group services, and from Spark driver and executor allocations. 

Note: Hosts will only be blocked from Spark driver and executor allocations which are active when the hosts are added. To block hosts from allocations which are created after the hosts join the cluster, use the egosh alloc block command. See the egosh command reference for more information.

Default value: OFF

 

ASC_AUTO_OPEN_NEW_HOSTS

Description: Specifies whether hosts should be opened when they are added to a resource group, after they have been blocked from all application instance and instance group services and Spark driver and executor allocations. If ASC_AUTO_BLOCK_NEW_HOSTS=OFF, this parameter has no effect.

Default value: OFF

 

ASC_AUTO_UNBLOCK_HOSTS_AFTER_DEPLOY

Description: Specifies whether hosts should be automatically unblocked for an application instance or instance group after all packages for the instance have been successfully deployed on the host.

Default value: ON

To ensure that services and Spark workload are not attempted on a new host joining the cluster, it is recommended that the hosts join the cluster in closed state so that they can be blocked before they are opened. To achieve this:

1.      Set the following configuration in the $EGO_CONFDIR/../../ascd/conf/ascd.conf file:

            ASC_AUTO_BLOCK_NEW_HOSTS=ON

      ASC_AUTO_OPEN_NEW_HOSTS=ON

2.      Set the following in the $EGO_CONFDIR/ego.conf file:

            EGO_NEW_HOST_WITH_CLOSED_STATUS=Y

For more information on setting ego.conf parameters, see the ego.conf reference.

3.      Restart EGO on all management hosts for the setting to take effect.

 

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

RFE 142803 – Enable parallel deployment on started instance groups.

RFE 142804 – Blocking host participation in any cluster activity.

2.     Download location

Download interim fix 552361 from the following location: https://www.ibm.com/eserver/support/fixes/

3.     Product and components affected

Component name, Platform, Fix ID:

ascd and WEBGUI, Linux x86_64, sc-2.4.1-build552361

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 master host as the cluster administrator and stop the WEBGUI and REST services:

> egosh user logon -u Admin -x Admin

> egosh service stop WEBGUI ascd

b)       On each of your management hosts, download and extract the following two packages to, for example, for example, a /scfixes directory:
ascd-2.4.1.0_noarch_build552361.tar.gz
conductorsparkmgmt-2.4.1.0_noarch_build552361.tar.gz

c)       On each of your management hosts, run the egoinstallfixes command to install the downloaded packages:

> egoinstallfixes /scfixes/ascd-2.4.1.0_noarch_build552361.tar.gz

> egoinstallfixes /scfixes/conductorsparkmgmt-2.4.1.0_noarch_build552361.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 management hosts, run the pversions command to verify the installation:

> pversions -b 552361

e)    Edit the $EGO_CONFDIR/../../ascd/conf/ascd.conf file to add the following lines:

    ASC_ALLOW_DEPLOY_IN_STARTED_STATE=ON
ASC_AUTO_BLOCK_NEW_HOSTS=ON
ASC_AUTO_OPEN_NEW_HOSTS=ON

f)    Clear your browser cache. 

g)   From the master host, start the WEBGUI and REST services:

> egosh service start WEBGUI ascd

5.     Uninstallation

If required, follow the instructions in this section to uninstall this interim fix from your cluster.

a)       Log on to the master host as the cluster administrator and stop the WEBGUI and REST services:

> egosh user logon -u Admin -x Admin

> egosh service stop WEBGUI ascd

b)       On each management host, roll back this interim fix:

> egoinstallfixes -r 552361

c)    Edit the $EGO_CONFDIR/../../ascd/conf/ascd.conf file to remove the following lines:

    ASC_ALLOW_DEPLOY_IN_STARTED_STATE=ON
ASC_AUTO_BLOCK_NEW_HOSTS=ON
ASC_AUTO_OPEN_NEW_HOSTS=ON

d)    Clear your browser cache. 

e)    From the master host, start the WEBGUI and REST services:

> egosh service start WEBGUI ascd

6.     List of files

$EGO_TOP/ascd/2.4.1/lib/asc-common-2.4.1.jar

$EGO_TOP/ascd/2.4.1/lib/asc-core-2.4.1.jar

$EGO_TOP/wlp/usr/servers/gui/apps/conductor/2.4.1/conductorgui/spark/instance/i18n/locale-en.json

$EGO_TOP/wlp/usr/servers/gui/apps/conductor/2.4.1/conductorgui/spark/instance/js/instanceView.controller.js

$EGO_TOP/wlp/usr/servers/gui/apps/conductor/2.4.1/conductorgui/spark/instance/js/instanceViewHosts.controller.js

$EGO_TOP/wlp/usr/servers/gui/apps/conductor/2.4.1/conductorgui/spark/instance/instanceViewHosts.html

$EGO_TOP/wlp/usr/servers/gui/apps/conductor/2.4.1/conductorgui/spark/instance/instanceViewOverview.html

$EGO_TOP/wlp/usr/servers/gui/apps/conductor/2.4.1/conductorgui/anaconda/distributions/js/distributionView.controller.js

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.