Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4133

DbCachingRemoteDirectory / RemoteDirectoryCacheRefresher noisy logging

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Support tools
    • 3
    • 6
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      I see logs like this in PUG every hour:

      @4000000054666294350ce114 2014-11-15 07:14:02,887 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 163841 ] starting
      @4000000054666294350ceccc 2014-11-15 07:14:02,888 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 163841 ]
      @4000000054666294350cf0b4 2014-11-15 07:14:02,889 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Incremental synchronisation for directory [ 163841 ] was not completed, falling back to a full synchronisation
      @400000005466629435475dbc 2014-11-15 07:14:02,889 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 163841 ] was not successful, attempting FULL
      @4000000054666296076666cc 2014-11-15 07:14:04,123 INFO [scheduler_Worker-4] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteUsers found [ 1388 ] remote users in [ 1233 ms ]
      @4000000054666296102c5f8c 2014-11-15 07:14:04,270 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedUsersNotIn scanned and compared [ 1388 ] users for delete in DB cache in [ 145ms ]
      @4000000054666296103091c4 2014-11-15 07:14:04,271 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedUsersNotIn scanned for deleted users in [ 146ms ]
      @400000005466629612a9abfc 2014-11-15 07:14:04,312 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] getUsersToAddAndUpdate scanning [ 1388 ] users to add or update
      @400000005466629613ddcae4 2014-11-15 07:14:04,332 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedUsers scanned and compared [ 1388 ] users for update in DB cache in [ 50ms ]
      @400000005466629613e7f08c 2014-11-15 07:14:04,333 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedUsers synchronised [ 1388 ] users in [ 51ms ]
      @40000000546662961938bbd4 2014-11-15 07:14:04,422 INFO [scheduler_Worker-4] [directory.ldap.cache.RemoteDirectoryCacheRefresher] findAllRemoteGroups found [ 27 ] remote groups in [ 89 ms ]
      @40000000546662961938c78c 2014-11-15 07:14:04,422 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedGroups scanning [ 27 ] groups to add or update
      @400000005466629619b4602c 2014-11-15 07:14:04,430 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] findGroupsToUpdate scanned and compared [ 27 ] groups for update in DB cache in [ 7ms ]
      @400000005466629619c25a4c 2014-11-15 07:14:04,431 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations] addOrUpdateCachedGroups synchronized [ 27 ] groups in [ 8ms ]
      @400000005466629619fb19a4 2014-11-15 07:14:04,435 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteChangeOperations] deleteCachedGroupsNotIn scanned and compared [ 27 ] groups for delete in DB cache in [ 3ms ]
      @400000005466629a10470bac 2014-11-15 07:14:08,271 INFO [scheduler_Worker-4] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache FULL synchronisation complete for directory [ 163841 ] in [ 5384ms ]
      

      Looking at these messages, I'm not convinced there's anything particularly INFO-worthy in there. Sure - it found some users in the remote directory, it found some groups in the remote directory, it tried to see if any local users/groups needed to be added or removed. It didn't find any.

      I would propose the following:

      • A single INFO level log on the hour to indicate that a sync is taking place (basically, the first log line in the output above is fine).
      • Everything else should be DEBUG level.
      • Any user deletion / creation should be INFO level.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sday@atlassian.com Samuel Day (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: