Bug 1288132
Summary: | Same 'Completed indexing' message 3 times in the server log | ||
---|---|---|---|
Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Zuzana Krejčová <zkrejcov> |
Component: | Business Central | Assignee: | manstis |
Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | lpetrovi |
Target Milestone: | DR1 | ||
Target Release: | 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-27 19:42:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Zuzana Krejčová
2015-12-03 15:57:40 UTC
Business Central is actually indexing 'repository1' three times:- 16:11:25,028 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 8) Starting indexing of default://master@repository1/ ... 16:11:25,030 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 5) Starting indexing of default://master@datasets/ ... 16:11:25,030 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 7) Starting indexing of default://master@repository1/ ... 16:11:25,034 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 4) Starting indexing of default://master@repository1/ ... ... 16:11:27,004 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 4) Completed indexing of default://master@repository1/ 16:11:27,004 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 8) Completed indexing of default://master@repository1/ 16:11:27,183 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 7) Completed indexing of default://master@repository1/ This should not be happening! (In reply to manstis from comment #1) > Business Central is actually indexing 'repository1' three times:- > > 16:11:25,028 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 8) Starting indexing of default://master@repository1/ ... > 16:11:25,030 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 5) Starting indexing of default://master@datasets/ ... > 16:11:25,030 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 7) Starting indexing of default://master@repository1/ ... > 16:11:25,034 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 4) Starting indexing of default://master@repository1/ ... > ... > 16:11:27,004 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 4) Completed indexing of default://master@repository1/ > 16:11:27,004 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 8) Completed indexing of default://master@repository1/ > 16:11:27,183 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - > 7) Completed indexing of default://master@repository1/ > > This should not be happening! Hmm, I didn't even see that in all the server log noise. Luckily it doesn't change the fact that it seems to not cause any problems. And the repo is pretty much empty at that time. I also haven't seen this happen for any other repository. The cause is that multiple requests are made for the "repository1" FileSystem before the batch indexing has flagged that batch indexing is "in progress"; hence multiple batch indexing takes place. There is little risk running multiple batch indexing of the same FileSystem; it's just wasteful. The three batch indexing observed are caused by:- 1 - Creating "repository1" repository. 2 - jBPM Designer writing a "global" folder to "repository1". 3 - system.git changed (as a result of "repository1" being added). Now I see the repository1 indexing just 2 times instead of 3. |