Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent Results from Asset Indexing (w/ Redis sessions) #3450

Closed
timkelty opened this issue Nov 7, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@timkelty
Copy link
Contributor

commented Nov 7, 2018

You will end up with certain items not indexed, and the message at the end prompting you for missing files that are actually there.

maxConcurrentActions: 3 in the js is the culprit: https://github.com/craftcms/cms/blob/develop/src/web/assets/assetindexes/dist/AssetIndexesUtility.js#L191

Because of the way the indexer steps through the assetindexdata, it doesn't really jive with any sort of concurrency.

This may only be apparent when you are running nginx+php-fpm, as request are handled in a pool, so there is no guarantee of synchronous execution.

A good reason to bump #2980 to the top of the 3.x list if you ask me :)

@timkelty

This comment has been minimized.

Copy link
Contributor Author

commented Mar 4, 2019

@andris-sevcenko this is definitely still an issue, please reopen.

The index-assets/one cli command works consistently and as expected.
The web utility indexes inconsistently.

Screencast of web utility/CLI: https://drive.google.com/file/d/1p-neAYKnaPrS7X6Ugz24k2-Grm3d0Drz/view

Related: #2876

@andris-sevcenko

This comment has been minimized.

Copy link
Member

commented Mar 5, 2019

@timkelty any chance of getting the CP access to the site? support@craftcms.com, as usual!

@timkelty timkelty changed the title Inconsistent Results from Asset Indexing (w/ nginx+fpm) Inconsistent Results from Asset Indexing (w/ Redis sessions) Mar 7, 2019

@timkelty

This comment has been minimized.

Copy link
Contributor Author

commented Mar 7, 2019

Thanks @andris-sevcenko

For anyone else finding this thread, having a centralized sessioncomponent (\yii\redis\Session) was what triggered this behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.