Lexorank Management "Next Rebalance" status is confusing

XMLWordPrintable

    • 1
    • 4

      Problem Definition

      In LexoRank Managment UI, (System > Lexorank management.), there is a Rank Status column, the "Next Rebalance" status "scheduled" is confusing / unintuitive.

       

      According to Documentation the Next Rebalance will be scheduled, when Status is "Warning".

      Status
      OK the rank length is in a healthy state
      Warning a rebalance has been scheduled
      Critical an immediate rebalance has started, you are approaching a state where rank operations will be disabled

      When is a re-balance job is triggered or required?
      When the the ranking value splits in 2 different buckets.
      The number of characters on the lengthiest rank field on the table is what defines the need for a rebalance operation, and here are the thresholds:

      • 50 characters: a rebalance operation is scheduled to occur in 12 hours;
      • 100 characters: a rebalance operation is immediately started;
      • Issues with > 254 characters RANK can't be ranked.

      But we also have this on the documentation: 

      Next rebalance
      Scheduled
      • once the next threshold is reached, a rebalance will be scheduled
      Immediate
      • once the next threshold is reached, a rebalance will start immediately

      Suggested Solution

      We need better "Next Rebalance" statuses, when Rank Status = OK. then "Next Rebalance" Status should be something like "Not scheduled”, so we can make this message more intuitive, less confusing for admins.

      Also, Additionally documentation may be provided/updated to clarify on the different balancing statuses available, and what are the threshold / limits that will trigger the re-balance.

      Or an information dialogue that the admin can hover a mouse over to learn more about what the status means.

              Assignee:
              Unassigned
              Reporter:
              Diego Baeza (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: