Please enable JavaScript.

Coggle requires JavaScript to display documents.

WEB-27036 Multitenant - Load balancing, Stop the ETL service, Stop the…

- - - - Start the ETL service
        
        The oldest rows from the 'Tenant_B' are deleting
        
        The oldest rows from the 'Tenant_A' are deleting
        
        No related error records in the CaseIngestionQueueErrorRecords table
        
        Scale
        
        1 - T10097
        
        2 - T10094
    - - Active -T10094
      - Not Active - T10097
- - - - Start the Indexer service
        
        The oldest rows from the 'Tenant_B' are deleting
        
        The oldest rows from the 'Tenant_A' are deleting
        
        No related error records in the IndexerQueueRecords table
        
        Scale
        
        1 - T10093
        
        2 - T10096
    - - Active - T10096
      - Not Active - T10093
- - - - Start the Playbook service
        
        The oldest rows from the 'Tenant_B' are deleting
        
        The oldest rows from the 'Tenant_A' are deleting
        
        No related error records in the
        WorkflowQueueRecords table
        
        Scale
        
        1 - T10092
        
        2 - T10095
    - - Active - T10095
      - Not Active - T10092
- - - - Ingest few alerts to 'Tenant_B'
        The table of 'caseIngestionQueueRecords' should contain 100 records of that tenant
        
        Observe the siemplify_system_db > 'InvolvedThreatIndicators' table
        
        Start the ETL service
        
        Stop the ETL service when the table contain 200 records (rows)
        
        Tenant_A should have approximately 180 records
        Tenant_A should have approximately 20 records
- - - - Ingest a lot of alerts into 'Tenant_A'
        The table of 'WorkFlowQueueRecords' should contain 1,000 records of that tenant
        
        Ingest few alerts to 'Tenant_B'
        The table of 'WorkFlowQueueRecords' should contain 100 records of that tenant
        
        Observe the siemplify_system_db > 'WorkFlowDoneRecords' table
        
        Start the Playbook service
        
        Stop the ETL service when the table contain 200 records (rows)
        
        Tenant_A should have approximately 180 records
        Tenant_A should have approximately 20 records
- - - - Ingest a lot of alerts into 'Tenant_A'
        The table of 'IndexerQueueRecords' should contain at least 1,000 records of that tenant
        
        Ingest few alerts to 'Tenant_B'
        The table of 'IndexerQueueRecords' should contain at least 100 records of that tenant
        
        Observe the siemplify_system_db > 'IndexerDoneRecords' table
        
        Start the Indexer service
        
        Stop the ETL service when the table contain 200 records (rows)
        
        Tenant_A should have approximately 180 records
        Tenant_A should have approximately 20 records
- - - - Delete tenant 'Tenant_A'
        
        Check that the row of 'Tenant_A' is deleted from the 'QueueWeights' table
- - - - Go to siemplify_queus_db > QueueWeights
        
        See that on each tenant the weight is '1'
        
        Change the weight of 'Tenant_A' to 9
        
        Change the weight of 'Tenant_B' to 1
        
        Ingest a lot of alerts into 'Tenant_A'
        The table of 'caseIngestionQueueRecords' should contain 1,000 records of that tenant
        
        Ingest few alerts to 'Tenant_B'
        The table of 'caseIngestionQueueRecords' should contain 100 records of that tenant
        
        1 more item...