Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-9134

Synchronisation of clustered controllers with Kie servers not working

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 7.34.0.Final
    • Cloud
    • None
    • NEW
    • NEW
    • Hide
      • Deploy authoring-ha environment using ControllerBasedStartupStrategy
      • Deploy a project using Workbench

      This project might not be available in all Kie Servers. It depends on what Kie Servers are connected with each Business Central.

      Show
      Deploy authoring-ha environment using ControllerBasedStartupStrategy Deploy a project using Workbench This project might not be available in all Kie Servers. It depends on what Kie Servers are connected with each Business Central.

    Description

      When using the ControllerBasedStartupStrategy strategy and having multiple Business Central instances, these are not synchronised with each other. So, each Business Central will connect only with the Kie Servers instances that are connected with, without taking into account others Kie Servers that might be connected with others Business Centrals.

      This mainly affects to authoring-ha environments where there are multiple Business Centrals.

      This issue was first raised as part of JBPM-6601 and the resolution was not doing it. Instead, we configured the authoring-ha environments to use the OpenShiftStartupStrategy strategy which works fine when having multiple Business Centrals but requires the Kie Server to be restarted in every project change.

      Precisely, many users complained about Kie Servers restarts when using OpenShiftStartupStrategy (see RHDM-1151) and we configured back the strategy to ControllerBasedStartupStrategy for 7.7.0 (for RHDM-1167 and RHPAM-2567). Therefore, we went back to the loop, same problem of synchronisation was back and we had to revert both RHDM-1167 and RHPAM-2567 tickets in 7.7.1 (RHPAM-2830)

      This ticket is about to provide a solution to fix the ControllerBasedStartupStrategy to make it able to synchronise multiple Business Centrals.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. RHDM-1151 KIE-Server restarts on OpenShift when doing a deployment from Business Central

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2919 Kie Servers are not synchronised with each other

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBPM-6601 Synchronization of clustered controllers with Kie servers using WebSockets

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2830 Business Central are not synchronised with each other (also Kie Servers)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHDM-1167 Change authoring environment to Controller strategy

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHPAM-2567 Remove ReadWriteMany requirement from non-HA Authoring environment and switch all Authoring templates to Controller strategy

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-support-fspolti Filippe Spolti
              jcarvaja@redhat.com Jose Carvajal Hilario
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: