Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-1352

ORIGINATORID value can churn too quickly.

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Middleware
    • Labels:
      None

      Description

      The ORIGINATORID is a 64-bit word consisting of an IPv4 host address, 16-bit process id, and 16-bit local value. In addition to the 16-bit process id not being standard across platforms (Mac OS >Leopard goes to 99999), the churn rate for the local value should be much higher than just 16 bits.

      This could be fixed to changing ORIGINATORID to a 32-bit process id and a separate value for the local value, which would be specified together in the DM event selector. I have to look into this more to see if this is a viable solution.

      This might need to go to three separate values to future proof it (i.e., ipv6).

        Attachments

          Issue Links

            Activity

            spietrowicz Steve Pietrowicz created issue -
            spietrowicz Steve Pietrowicz made changes -
            Field Original Value New Value
            Epic Link DM-1121 [ 13930 ]
            spietrowicz Steve Pietrowicz made changes -
            Team Middleware [ 10206 ]
            spietrowicz Steve Pietrowicz made changes -
            Description The ORIGINATORID is a 64-bit word consisting of an IPv4 host address, 16-bit process id, and 16-bit local value. In addition to the 16-bit process id not being standard across platforms (Mac OS >Leopard goes to 99999), the churn rate for the local value should be much higher than just 16 bits.

            This could be fixed to changing ORIGINATORID to a 32-bit process id and a separate value for the local value, which would be specified together in the DM event selector. I have to look into this more to see if this is a viable solution.
            The ORIGINATORID is a 64-bit word consisting of an IPv4 host address, 16-bit process id, and 16-bit local value. In addition to the 16-bit process id not being standard across platforms (Mac OS >Leopard goes to 99999), the churn rate for the local value should be much higher than just 16 bits.

            This could be fixed to changing ORIGINATORID to a 32-bit process id and a separate value for the local value, which would be specified together in the DM event selector. I have to look into this more to see if this is a viable solution.

            This might need to go to three separate values to future proof it (i.e., ipv60.
            spietrowicz Steve Pietrowicz made changes -
            Description The ORIGINATORID is a 64-bit word consisting of an IPv4 host address, 16-bit process id, and 16-bit local value. In addition to the 16-bit process id not being standard across platforms (Mac OS >Leopard goes to 99999), the churn rate for the local value should be much higher than just 16 bits.

            This could be fixed to changing ORIGINATORID to a 32-bit process id and a separate value for the local value, which would be specified together in the DM event selector. I have to look into this more to see if this is a viable solution.

            This might need to go to three separate values to future proof it (i.e., ipv60.
            The ORIGINATORID is a 64-bit word consisting of an IPv4 host address, 16-bit process id, and 16-bit local value. In addition to the 16-bit process id not being standard across platforms (Mac OS >Leopard goes to 99999), the churn rate for the local value should be much higher than just 16 bits.

            This could be fixed to changing ORIGINATORID to a 32-bit process id and a separate value for the local value, which would be specified together in the DM event selector. I have to look into this more to see if this is a viable solution.

            This might need to go to three separate values to future proof it (i.e., ipv6).
            spietrowicz Steve Pietrowicz made changes -
            Sprint W15 Dec Sprint 3 [ 117 ]
            spietrowicz Steve Pietrowicz made changes -
            Story Points 2
            spietrowicz Steve Pietrowicz made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]
            mgelman2 Margaret Gelman made changes -
            Sprint W15 Dec Sprint 3 [ 117 ] W15 Dec Sprint 3, W15 Jan Sprint 1 [ 117, 121 ]
            mgelman2 Margaret Gelman made changes -
            Rank Ranked higher
            spietrowicz Steve Pietrowicz made changes -
            Rank Ranked lower
            spietrowicz Steve Pietrowicz made changes -
            Parent DM-1350 [ 14355 ]
            Issue Type Story [ 10001 ] Technical task [ 10002 ]
            spietrowicz Steve Pietrowicz made changes -
            Epic Link DM-1121 [ 13930 ]
            spietrowicz Steve Pietrowicz made changes -
            Resolution Done [ 10000 ]
            Status In Progress [ 3 ] Done [ 10002 ]
            spietrowicz Steve Pietrowicz made changes -
            Story Points 2 8
            spietrowicz Steve Pietrowicz made changes -
            Parent DM-1350 [ 14355 ]
            Issue Type Technical task [ 10002 ] Story [ 10001 ]
            spietrowicz Steve Pietrowicz made changes -
            Epic Link DM-1121 [ 13930 ]
            spietrowicz Steve Pietrowicz made changes -
            Link This issue relates to DM-1350 [ DM-1350 ]
            frossie Frossie Economou made changes -
            Team Process Middleware [ 10206 ] Data Facility [ 12219 ]

              People

              Assignee:
              spietrowicz Steve Pietrowicz
              Reporter:
              spietrowicz Steve Pietrowicz
              Watchers:
              Kian-Tat Lim, Steve Pietrowicz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  CI Builds

                  No builds found.