Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1044

Smart router nodes in OpenShift don't share data

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.0.0.GA
    • 7.0.0.GA
    • Kie-Server

    • OpenShift
      persistent volumes using Gluster or NFS

    • CR1
    • CR2
    • Hide

      Deploy 2 Smart router pods [1] into the OpenShift backed by NFS or Gluster. Start one Kie server configured to connect to the Smart router. Check Smart routers inner state using curl on the pods.
      =>
      Their state is inconsistent even though the config file content is same on both pods.

      [1] https://github.com/jboss-container-images/rhpam-7-openshift-image/blob/rhpam70-dev/templates/rhpam70-prod-immutable-monitor.yaml

      Show
      Deploy 2 Smart router pods [1] into the OpenShift backed by NFS or Gluster. Start one Kie server configured to connect to the Smart router. Check Smart routers inner state using curl on the pods. => Their state is inconsistent even though the config file content is same on both pods. [1] https://github.com/jboss-container-images/rhpam-7-openshift-image/blob/rhpam70-dev/templates/rhpam70-prod-immutable-monitor.yaml

    Description

      The issue happens on Smart router nodes deployed in OpenShift using persistent volumes backed by Gluster or NFS.
      The problem is that even though the nodes share the same config file their inner configuration isn't updated. It may be caused by incompatibility between WatchService (used for monitoring of shared config file) and remote file systems [1]. The root issue may be related to inotify interactions with remote filesystems [2]

      [1] https://stackoverflow.com/questions/11628584/jdk-7-watch-service-api-and-nfs-file-sharing
      [2] https://stackoverflow.com/questions/4231243/inotify-with-nfs/4231277#4231277

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-294 Process can't be execute in Kie Server S2I in unmanaged mode.

          • 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

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-1149 Synchronization issue for concurrent registrations in Smart router

          • 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-rromerom Ruben Romero Montes
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: