Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-23021

Add debug logging in redis.retry.Retry

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 8.10, 9.2
    • Fix Version/s: 8.10-HF16, 9.3
    • Component/s: Redis
    • Release Notes Summary:
      Debug logs are added in retry mechanism for Redis
    • Backlog priority:
      500
    • Sprint:
      nxcore 9.3.6
    • Story Points:
      1

      Description

      In org.nuxeo.ecm.core.redis.retry.Retry , within public <T> T retry(Block<T> block, Policy policy) , we can spot a need for additional logging in case of getting exceptions.

      This is also the case in org.nuxeo.ecm.core.redis.RedisFailoverExecutor , within protected <T> T executeWithRetryPolicy(final RedisCallable<T> callable, Retry.Policy policy) / @Override public T retry()

      The problem we are trying to solve is the following: no log but getting forever the stack dump:

      at java.lang.Thread.sleep(Native Method)
      at org.nuxeo.ecm.core.redis.retry.SimpleDelay.pause(SimpleDelay.java:45)
      at org.nuxeo.ecm.core.redis.retry.Retry.retry(Retry.java:68)
      at org.nuxeo.ecm.core.redis.RedisFailoverExecutor.executeWithRetryPolicy(RedisFailoverExecutor.java:57)
      at org.nuxeo.ecm.core.redis.RedisFailoverExecutor.execute(RedisFailoverExecutor.java:43)
      at org.nuxeo.ecm.core.redis.contribs.RedisWorkQueuing.listWorkSet(RedisWorkQueuing.java:724)
      at org.nuxeo.ecm.core.redis.contribs.RedisWorkQueuing.listRunning(RedisWorkQueuing.java:280)
      at org.nuxeo.ecm.core.redis.contribs.RedisWorkQueuing.listWork(RedisWorkQueuing.java:249)
      at org.nuxeo.ecm.core.work.WorkManagerImpl.listWork(WorkManagerImpl.java:824)
      

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 20 minutes
                20m