Magento 2 Is it possible to run reindexing per storeview?

Clash Royale CLAN TAG#URR8PPP

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
2
down vote

favorite

1

My site has more than 100.000 products and almost 20 storeviews. Each time I run a full reindexing, it takes about 10 hours for reindexing to be finished.

I wonder if it's possible to just run reindexing for a specific storeview?

magento2 reindex indexing

share|improve this question

asked 2 hours ago

Magento Learner

623718

add a comment | 

up vote
2
down vote

favorite

1

My site has more than 100.000 products and almost 20 storeviews. Each time I run a full reindexing, it takes about 10 hours for reindexing to be finished.

I wonder if it's possible to just run reindexing for a specific storeview?

magento2 reindex indexing

share|improve this question

asked 2 hours ago

Magento Learner

623718

add a comment | 

up vote
2
down vote

favorite

1

up vote
2
down vote

favorite

1

1

My site has more than 100.000 products and almost 20 storeviews. Each time I run a full reindexing, it takes about 10 hours for reindexing to be finished.

I wonder if it's possible to just run reindexing for a specific storeview?

magento2 reindex indexing

share|improve this question

asked 2 hours ago

Magento Learner

623718

My site has more than 100.000 products and almost 20 storeviews. Each time I run a full reindexing, it takes about 10 hours for reindexing to be finished.

I wonder if it's possible to just run reindexing for a specific storeview?

magento2 reindex indexing

magento2 reindex indexing

share|improve this question

asked 2 hours ago

Magento Learner

623718

share|improve this question

asked 2 hours ago

Magento Learner

623718

share|improve this question

share|improve this question

asked 2 hours ago

Magento Learner

623718

asked 2 hours ago

Magento Learner

623718

asked 2 hours ago

Magento Learner

623718

623718

add a comment | 

add a comment | 

1 Answer
1

active

oldest

votes

up vote
3
down vote



accepted

There is no direct way to do this. But you may be approaching it from the wrong angle anyway.

In normal operation you shouldn't have to do a full reindex at any time. If you have the indexing mode set to schedule, triggers in the database will create records in the _cl (changelog) tables on data modification.

The mview_state table keeps track of which changes have been handled so far.

The indexer cron jobs (indexer_reindex_all_invalid) which normally runs every minute / 5 minutes. Will automatically reindex all the pending changes - and clear the caches of those specific items.

So you won't have to ever do a full reindex. If you switch the indexer mode to realtime (Update on save). The triggers get removed from the database and magento will trigger reindexing and cache clearing on save.
This is extremely bad, because it will do a full reindex / cache clear on the save of a single product/category/etc. This is behavior you (almost) never want to have.

So my advice would be:

• Set the indexer mode to schedule (bin/magento indexer:set-mode schedule)


• Make sure the default magento cron jobs are running every minute/5 minutes


• Do not reindex manually. If you must do this, before reindexing set the indexer mode to realtime bin/magento indexer:set-mode realtime, reset the index bin/magento indexer:reset, run the reindex, then switch back to schedule mode.


• If you have no cron jobs scheduled on like a dev environment, simpley run the cron jobs manaully when you have to update the index (bin/magento cron:run)

John Hughes has an excellent talk on this subject at magento conferences. You can read his presentation sheets here. It's really insightful stuff, and well worth a read:

https://docs.google.com/presentation/d/1NdtNz_LBxk-JsCBy8AvekZAkSPWOE0WCzE14Y9ki-5Q/mobilepresent?slide=id.g3444c1e91c_0_10

share|improve this answer

edited 19 mins ago

answered 44 mins ago

Rick Schippers

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "",
contentPolicyHtml: "",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f248556%2fmagento-2-is-it-possible-to-run-reindexing-per-storeview%23new-answer', 'question_page');

);

Post as a guest

Name Email

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
3
down vote



accepted

There is no direct way to do this. But you may be approaching it from the wrong angle anyway.

In normal operation you shouldn't have to do a full reindex at any time. If you have the indexing mode set to schedule, triggers in the database will create records in the _cl (changelog) tables on data modification.

The mview_state table keeps track of which changes have been handled so far.

The indexer cron jobs (indexer_reindex_all_invalid) which normally runs every minute / 5 minutes. Will automatically reindex all the pending changes - and clear the caches of those specific items.

So you won't have to ever do a full reindex. If you switch the indexer mode to realtime (Update on save). The triggers get removed from the database and magento will trigger reindexing and cache clearing on save.
This is extremely bad, because it will do a full reindex / cache clear on the save of a single product/category/etc. This is behavior you (almost) never want to have.

So my advice would be:

• Set the indexer mode to schedule (bin/magento indexer:set-mode schedule)


• Make sure the default magento cron jobs are running every minute/5 minutes


• Do not reindex manually. If you must do this, before reindexing set the indexer mode to realtime bin/magento indexer:set-mode realtime, reset the index bin/magento indexer:reset, run the reindex, then switch back to schedule mode.


• If you have no cron jobs scheduled on like a dev environment, simpley run the cron jobs manaully when you have to update the index (bin/magento cron:run)

John Hughes has an excellent talk on this subject at magento conferences. You can read his presentation sheets here. It's really insightful stuff, and well worth a read:

https://docs.google.com/presentation/d/1NdtNz_LBxk-JsCBy8AvekZAkSPWOE0WCzE14Y9ki-5Q/mobilepresent?slide=id.g3444c1e91c_0_10

share|improve this answer

edited 19 mins ago

answered 44 mins ago

Rick Schippers

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

up vote
3
down vote



accepted

There is no direct way to do this. But you may be approaching it from the wrong angle anyway.

In normal operation you shouldn't have to do a full reindex at any time. If you have the indexing mode set to schedule, triggers in the database will create records in the _cl (changelog) tables on data modification.

The mview_state table keeps track of which changes have been handled so far.

The indexer cron jobs (indexer_reindex_all_invalid) which normally runs every minute / 5 minutes. Will automatically reindex all the pending changes - and clear the caches of those specific items.

So you won't have to ever do a full reindex. If you switch the indexer mode to realtime (Update on save). The triggers get removed from the database and magento will trigger reindexing and cache clearing on save.
This is extremely bad, because it will do a full reindex / cache clear on the save of a single product/category/etc. This is behavior you (almost) never want to have.

So my advice would be:

• Set the indexer mode to schedule (bin/magento indexer:set-mode schedule)


• Make sure the default magento cron jobs are running every minute/5 minutes


• Do not reindex manually. If you must do this, before reindexing set the indexer mode to realtime bin/magento indexer:set-mode realtime, reset the index bin/magento indexer:reset, run the reindex, then switch back to schedule mode.


• If you have no cron jobs scheduled on like a dev environment, simpley run the cron jobs manaully when you have to update the index (bin/magento cron:run)

John Hughes has an excellent talk on this subject at magento conferences. You can read his presentation sheets here. It's really insightful stuff, and well worth a read:

https://docs.google.com/presentation/d/1NdtNz_LBxk-JsCBy8AvekZAkSPWOE0WCzE14Y9ki-5Q/mobilepresent?slide=id.g3444c1e91c_0_10

share|improve this answer

edited 19 mins ago

answered 44 mins ago

Rick Schippers

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

up vote
3
down vote



accepted

up vote
3
down vote



accepted

There is no direct way to do this. But you may be approaching it from the wrong angle anyway.

In normal operation you shouldn't have to do a full reindex at any time. If you have the indexing mode set to schedule, triggers in the database will create records in the _cl (changelog) tables on data modification.

The mview_state table keeps track of which changes have been handled so far.

The indexer cron jobs (indexer_reindex_all_invalid) which normally runs every minute / 5 minutes. Will automatically reindex all the pending changes - and clear the caches of those specific items.

So you won't have to ever do a full reindex. If you switch the indexer mode to realtime (Update on save). The triggers get removed from the database and magento will trigger reindexing and cache clearing on save.
This is extremely bad, because it will do a full reindex / cache clear on the save of a single product/category/etc. This is behavior you (almost) never want to have.

So my advice would be:

• Set the indexer mode to schedule (bin/magento indexer:set-mode schedule)


• Make sure the default magento cron jobs are running every minute/5 minutes


• Do not reindex manually. If you must do this, before reindexing set the indexer mode to realtime bin/magento indexer:set-mode realtime, reset the index bin/magento indexer:reset, run the reindex, then switch back to schedule mode.


• If you have no cron jobs scheduled on like a dev environment, simpley run the cron jobs manaully when you have to update the index (bin/magento cron:run)

John Hughes has an excellent talk on this subject at magento conferences. You can read his presentation sheets here. It's really insightful stuff, and well worth a read:

https://docs.google.com/presentation/d/1NdtNz_LBxk-JsCBy8AvekZAkSPWOE0WCzE14Y9ki-5Q/mobilepresent?slide=id.g3444c1e91c_0_10

share|improve this answer

edited 19 mins ago

answered 44 mins ago

Rick Schippers

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

There is no direct way to do this. But you may be approaching it from the wrong angle anyway.

In normal operation you shouldn't have to do a full reindex at any time. If you have the indexing mode set to schedule, triggers in the database will create records in the _cl (changelog) tables on data modification.

The mview_state table keeps track of which changes have been handled so far.

The indexer cron jobs (indexer_reindex_all_invalid) which normally runs every minute / 5 minutes. Will automatically reindex all the pending changes - and clear the caches of those specific items.

So you won't have to ever do a full reindex. If you switch the indexer mode to realtime (Update on save). The triggers get removed from the database and magento will trigger reindexing and cache clearing on save.
This is extremely bad, because it will do a full reindex / cache clear on the save of a single product/category/etc. This is behavior you (almost) never want to have.

So my advice would be:

• Set the indexer mode to schedule (bin/magento indexer:set-mode schedule)


• Make sure the default magento cron jobs are running every minute/5 minutes


• Do not reindex manually. If you must do this, before reindexing set the indexer mode to realtime bin/magento indexer:set-mode realtime, reset the index bin/magento indexer:reset, run the reindex, then switch back to schedule mode.


• If you have no cron jobs scheduled on like a dev environment, simpley run the cron jobs manaully when you have to update the index (bin/magento cron:run)

John Hughes has an excellent talk on this subject at magento conferences. You can read his presentation sheets here. It's really insightful stuff, and well worth a read:

https://docs.google.com/presentation/d/1NdtNz_LBxk-JsCBy8AvekZAkSPWOE0WCzE14Y9ki-5Q/mobilepresent?slide=id.g3444c1e91c_0_10

share|improve this answer

edited 19 mins ago

answered 44 mins ago

Rick Schippers

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this answer

share|improve this answer

edited 19 mins ago

edited 19 mins ago

edited 19 mins ago

answered 44 mins ago

Rick Schippers

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 44 mins ago

Rick Schippers

562

answered 44 mins ago

Rick Schippers

562

562

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

New contributor

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

Rick Schippers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f248556%2fmagento-2-is-it-possible-to-run-reindexing-per-storeview%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email