Skip to content

Issues Identified in MMCloud Jericho 3.1 Release

Known Issues and Limitations

  • Dashboard may display incorrect information if a user upgrades from release 3.0 (or earlier) to release 3.1 without running the database upgrade script on the OpCenter.

    Release 3.1 implements a SQL database for managing information related to past and current jobs. If the user upgrades from an earlier release and does not run /opt/memverge/sbin/opcenter_upgrade.sh on the OpCenter, the SQL database is not instantiated, resulting in the dashboard displaying incorrect information.
  • If the OpCenter submits a job that exceeds your AWS Service Quota, the job is marked as Failed and not requeued.

    AWS limits the resources you can use at any given time by imposing Service Quotas on your AWS account. If a Service Quota is exceeded for a short time and leads to a number of Failed jobs, the pipeline of which the jobs are components tends to fail.
  • If a spot instance migrates to a new spot instance because of manual migration or WaveRider event, the value defined by the maxSpotReclaim is ignored for subsequent spot interruptions.

    The vmPolicy option has a parameter (called maxSpotReclaim) that limits the number of spot interruptions allowed before the job moves to an on-demand instance. However, if a spot instance migrates to a new spot instance (because of a manual migration or a WaveRiding event), then the value of maxSpotReclaim is ignored for subsequent spot instance interruptions.