Merge pull request #275852 from msftrobiro/sap-upd-rhel-schedevents

SAP update scheduled events timeouts and add delay

Author: v-regandowner

articles/sap/workloads/get-started.md

@@ -55,6 +55,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- May 21, 2024: Update timeouts and added start delay for pacemaker scheduled events in [Set up Pacemaker on RHEL in Azure](./high-availability-guide-rhel-pacemaker.md) and [Set up Pacemaker on SUSE Linux Enterprise Server (SLES) in Azure](./high-availability-guide-suse-pacemaker.md).
 - April 1, 2024: Reference the considerations section for sizing HANA shared file system in [NFS v4.1 volumes on Azure NetApp Files for SAP HANA](./hana-vm-operations-netapp.md), [SAP HANA Azure virtual machine Premium SSD storage configurations](./hana-vm-premium-ssd-v1.md), [SAP HANA Azure virtual machine Premium SSD v2 storage configurations](./hana-vm-premium-ssd-v2.md), and [Azure Files NFS for SAP](planning-guide-storage-azure-files.md)
 - March 18, 2024: Added considerations for sizing the HANA shared file system in [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md)
 - February 07, 2024: Clarified disk allocation when using PPGs to bind availability set in specific Availability Zone in [Configuration options for optimal network latency with SAP applications](./proximity-placement-scenarios.md#combine-availability-sets-and-availability-zones-with-proximity-placement-groups)

articles/sap/workloads/high-availability-guide-rhel-pacemaker.md

@@ -488,8 +488,10 @@ When the cluster health attribute is set for a node, the location constraint tri
 
    ```bash
    sudo pcs resource create health-azure-events \
-   ocf:heartbeat:azure-events-az op monitor interval=10s
-   sudo pcs resource clone health-azure-events allow-unhealthy-nodes=true
+   ocf:heartbeat:azure-events-az \
+   op monitor interval=10s timeout=240s \
+   op start timeout=10s start-delay=90s
+   sudo pcs resource clone health-azure-events allow-unhealthy-nodes=true failure-timeout=120s
    ```
 
 1. Take the Pacemaker cluster out of maintenance mode.

articles/sap/workloads/high-availability-guide-suse-pacemaker.md

@@ -1037,7 +1037,7 @@ Azure offers [scheduled events](../../virtual-machines/linux/scheduled-events.md
    ```bash
    sudo crm configure primitive health-azure-events ocf:heartbeat:azure-events-az \ 
    meta allow-unhealthy-nodes=true failure-timeout=120s \ 
-   op start start-delay=90s \ 
+   op start start-delay=60s \ 
    op monitor interval=10s
 
    sudo crm configure clone health-azure-events-cln health-azure-events