Automic Workload Automation

 View Only

  • 1.  Rebuilding the Lucene indexes in AAKE

    Posted Jan 07, 2025 05:25 AM

    KB142556 describes how to rebuild the Lucene indexes, a step that can be necessary if the indexes become corrupted.

    How does one perform this operation in an AAKE system? Is it sufficient to restart the JWP with IDX role?

    Where does AAKE store the Lucene index? Is is stored in the JWP-IDX pod, or in some sort of persistent storage?



  • 2.  RE: Rebuilding the Lucene indexes in AAKE

    Posted Jan 08, 2025 03:19 AM
    Edited by Marcin Uracz Jan 08, 2025 03:19 AM

    Let me start with the second question first 

    > Where does AAKE store the Lucene index? Is is stored in the JWP-IDX pod, or in some sort of persistent storage?


    Both options are possible. 

    By default the Lucene index is stored locally in the POD(s) of the JWP with the appropriate role. But in the JWP section of the values.yml you can define also a PVC: 

      #configure the persistent volume claim to be used for mounting the index-cache folder.
      #index:
      #  pvc: "pvc-name"

    >How does one perform this operation in an AAKE system?

    Given the answer above you can imagine that the procedure will be different in both cases.

    If the Lucene index is local, then deleting the pod will be sufficient for the rebuild. 

    If the index is stored on PVC then that would need to be purged before deleting the PODs.

    I have not setup any AAKE environment like this, maybe the install-operator can / will handle this automatically?



    ------------------------------
    Cheers,
    Marcin
    ------------------------------



  • 3.  RE: Rebuilding the Lucene indexes in AAKE

    Posted Jan 08, 2025 06:50 AM
    Edited by Michael A. Lowry Jan 08, 2025 08:30 AM

    Thanks @Marcin Uracz. Using a PVC seems like a good idea, considering how long it takes to build the indexes from scratch.

    Broadcom Support: Would you please update KB142556 to include instructions for AAKE?



  • 4.  RE: Rebuilding the Lucene indexes in AAKE

    Posted Jan 20, 2025 03:35 AM
    Edited by Michael A. Lowry Jan 20, 2025 03:35 AM

    From what I was able to find in the documentation, the ability to specify a PVC for index cache storage was added in AAKE v24.2.

    What's New in Automic Automation v24.2.0

    Configuring your Automic Automation System before Deployment

    Is my understanding correct?



  • 5.  RE: Rebuilding the Lucene indexes in AAKE

    Posted Jan 30, 2025 03:04 AM

    Hello together,

    In addition to the points mentioned by Michael:

    In AAKE, the Lucene index will be rebuilt every time a new JWP pod is created. When a new pod is launched without any existing JWP pods in the deployment, a new Lucene index will be generated, and all previous indexes will be removed, provided that a PVC is not used during the deployment process.

    If a PVC is defined in the values.yaml (AAKE configuration file), the Lucene index memory will be stored in the PVC and reused as soon as a new JWP pod starts. The Lucene index memory will be stored in the PVC/JWP pod under either the 24_a or 24_b folder.

    If the index needs to be rebuilt, you can either delete or rename the 24_a or 24_b folder in the JWP pod or the PVC, then restart the JWP pod. This will clear the existing index memory and trigger the creation of a new index.

    The option to add a PVC for storing AE-related files such logs/traces/certs or indexes has always been available, but starting from V24.2, there is now the ability to assign separate PVCs for different AE processes in AAKE.