Known Issues for Protegrity Analytics

• Known Issue: Client side validation is missing on the Join an existing Audit Store Cluster page.

  Issue:

  Log in to the ESA Web UI and navigate to the Audit Store > Cluster Management > Overview page >Join Cluster. When you specify an invalid IP, enter a username or password more than the 36-character limit that is accepted on the Appliance, and click Join Cluster, then no errors are displayed and the request is processed.

  Observation:

  The Join an existing Audit Store Cluster page request is processed without any client-side validation, hence, an invalid IP address or a username or password more than 36 characters does not display any error.

• Known Issue: High memory usage on the ESA.

  Issue:

  When using the Audit Store, the memory usage is high on the ESA.

  Workaround:

  Reduce the memory usage by updating the memory allocated to the Audit Store on the ESA to 4 GB using the Set Audit Store Repository Total Memory CLI option.

  For more information about the Set Audit Store Repository Total Memory CLI option, refer to Setting the total memory for the Audit Store Repository.

• Known Issue: In Analytics, on the Index Lifecycle Management page, after exporting, importing, or deleting an index one of the following scenarios occurs:

  • The index operation performed does not appear in the other operation lists. For example, an exported index does not appear in the import index list.
  • Performing the same operation on the same index again displays an error message.
  • If the index appears in another operation list, performing the operation displays an error message. For example, an exported index appears in the delete index list and deleting the index displays an error.

  Issue: After performing an operation, the index list for the export, import, and delete operations does not refresh automatically.

  Workaround: Refresh the Index Lifecycle Management page after performing an export, import, or delete operation.

• Known Issue: The Specifying types in document update requests is deprecated, use the endpoint /{index}/_update/{id} instead. error message might appear during an upgrade.

  Issue: While upgrading, the error trace is logged while disabling the rollover index.

  Resolution: Ignore this message. It is a deprecation message and does not affect the upgrade or the functionality of the product.

• Known Issue: The Info: During upgrade, ignore errors related to unicast hosts file being empty. message might appear during an upgrade.

  Issue: While upgrading, the following errors might appear:

  • ERROR: Unicast hosts file does not contain the IP addresses of the nodes and is empty. Run the Audit Store Management Unicast Hosts scheduled task.
  • ERROR: Unicast hosts file is empty. Please add the IP and hostname entries for all the nodes in the Audit Store cluster in the Unicast hosts file /opt/protegrity/config/unicast_hosts.txt

  Resolution: Ignore this message. It does not affect the functionality of the product. The upgrade fixes the entries in the unicast hosts file and the upgrade completes successfully.

• Known Issue: The Info: While upgrading nodes in an Audit Store cluster, if the checks passed on one of the nodes, then ignore errors for the Audit Store cluster verification on the other nodes. message might appear during an upgrade.

  Issue: While upgrading, the following errors might appear:

  • ERROR: Audit Store version of the node across the cluster are inconsistent: {version}. Ensure the nodes are on the same ESA version.
  • ERROR: Expecting appliance version {Version number}.
  • ERROR: Expecting appliance version 10.1.X/10.0.X/9.2.0.X/9.1.0.X got {appliance_version}.
  • ERROR: Cluster health check failed. Current status: {cluster_status}.Resolve the cluster health to stabilize the cluster.
  • ERROR: Initializing shards check failed. Current value: {initializing_shards}. Wait till the shards are initialized and the value reaches zero.
  • ERROR: Relocating shards check failed. Current value: {relocating_shards}. Wait till the shards are automatically rebalanced and the value reaches zero.
  • ERROR: Unassigned shards check failed. Current value : {unassigned_shards}. Wait till the shards are processed and the value reaches zero.

  Resolution: If the checks passed on one of the nodes while upgrading nodes in an Audit Store cluster, then ignore the message if it appears on the other nodes. It does not affect the functionality of the product. The upgrade of the muilti-cluster nodes will complete successfully.