Skip to content

node id to hostname table entries are missing from hdb_analytics_hostname from some nodes #332

Description

@kylebernhardy

Bug Summary

Bad node value data coercion

Reproduction Repository (if applicable)

No response

Steps to Reproduce

This is reproducible in a private fabric environment, please connect with @kylebernhardy to get those details.

At a high level what we are seeing is one node in the cluster does have all of the correct node values in their analytics. The rest of the members of the cluster for the same node values appear to be performing an incorrect string - number coercion which cause this negative number. This will occur for any analytic.

sample prefix node names to bad number coercion look like (private data is X-ed out):
"846-fr-par-1.XXXXX.XXXXXX.harperfabric.com" -> -260125975

"xb6-us-west-1.XXXXX.XXXXXX.harperfabric.com" -> -1558863604

Expected Behavior

Data is preserved across the cluster

Actual Behavior

Data is being incorrectly coerced to number

Platform

Harper 4.7.25

Console Errors

No response

Screenshots or Videos

No response

Additional Context

No response

Are you planning to fix this issue?

No, just reporting the issue

First-time contributor support

  • I'm new to contributing and would appreciate guidance on the process
  • I'd like help understanding the project structure
  • I need assistance with setting up the development environment
  • I'm comfortable contributing, but new to this project specifically

Activity

  1. changed the title [-]Some node values in replicated analytics are being coerced incorrectly from string into a negative number[/-] [+]node id to hostname table entries are missing from hdb_analytics_hostname from some nodes[/+] on Apr 13, 2026
  2. kriszyp commented on Apr 13, 2026

    @kriszyp
    Member

    I don't think this ticket itself is directly actionable, this is related to older hostname records not being replicated (might be addressed by harper-pro#81, but also might not exist with modern configurations).

  3. added this to the v5.1 milestone on May 21, 2026
  4. modified the milestones: v5.1, v5.3 on Jul 23, 2026
  5. added theissue type on Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Fields

    Priority

    P2

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions