[MAGNOLIA-7108] users timezone permission delta task starts at root Created: 02/Sep/16  Updated: 04/Sep/17  Resolved: 31/Aug/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.7
Fix Version/s: 5.4.14, 5.5.7, 5.6

Type: Bug Priority: Minor
Reporter: Richard Gange Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
relation
is related to MGNLUI-2695 User can configure his timezone Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 109, Basel 110, Basel 111
Story Points: 5

 Description   

From the CoreModuleVersionHandler:

register((DeltaBuilder.update("5.4.7", ""))
                .addTask(new AddUsersPermissionTask("Allow users to edit their timezone setting", "/", RepositoryConstants.USERS, AddUsersPermissionTask.USER_PATH_REPLACEMENT + "/timezone", Permission.ALL)
                        .exclude(MgnlUserManager.SYSTEM_USER, MgnlUserManager.ANONYMOUS_USER))

Setting it to start at root causes it to crawl over jcr:system nodes. This can take a while for some customers.



 Comments   
Comment by Nicole Stutz [ 20/Jun/17 ]

Hi Richard

Our newest deployment from 5.3.17 to 5.4.12 seems to hang at this task. The logs does not show any indication what task is running (actually no log entries are shown), but as soon we shutdown the system this log entry is shown.

2017-06-20 15:01:36,728 ERROR info.magnolia.module.InstallContextImpl : [12/1043 tasks - Magnolia Core Module (version 5.4.12)]> Could not install or update core module. Task 'Allow users to edit their timezone setting' failed.

So, we guess, that our system was processing this update task. On Mysql, we see a lot of queries processing the "Version Bundle" table. At this moment we wait since more then 1h 30 min already, that the system may proceed. Do you think this is possible, it takes so long? You mention that it takes a while.

Our Version Store is about 12GB in size. Running a "SELECT count FROM VERSION BUNDLE" shows about 15 million rows.

Best Regards
Nicole

Comment by Federico Grilli [ 24/Aug/17 ]

Waiting after 5.5.6 release for integrating this.

Generated at Mon Feb 12 04:20:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.