[2.2.7, 2.2.8] - Indexer Schedule - backlog with product import

[jbrada]

If I import a product using the CSV import function, index changes are written to the backlog of:

• Product rule catalog
• Catalog Search
• Product price

even though the value has not changed (imported values are same as Magento 2 values).

This behavior did not affect either 2.2.5 or 2.2.6. This behavior occurs in versions 2.2.7 and 2.2.8.

Preconditions (*)

1. Magento 2.2.7 or Magento 2.2.8 (Not tested on 2.3.x versions) with sample data.
2. indexer:set-mode schedule

Steps to reproduce (*)

As an example, I will import only 2 fields: sku, qty

1. First import - The qty value is different from the original value.
   Backlog (1) for indexes

• Product rule catalog
• Cataog Search
• Product price
• Stock

2. Second import - The value is the same, there is no change
   Backlog (1) for indexes:

• Product rule catalog
• Cataog Search
• Product price

In this case, no index should be backlog (1) because there are no changes made.

Expected result (*)

Expected result if i import csv with no changes beside actual Magento 2 state.
(sku, qty)

Actual result (*)

Actual result if i import csv with no changes as actual Magento 2 state.

[m2-assistant]

Hi @higi90. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@higi90 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[m2-assistant]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99126, MAGETWO-99127 were created

Issue Available: @engcom-backlog-nazar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @verma-ankur. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[verma-ankur]

I am working on this at #dmcdindia1

[jaybouvet]

Hi !

What is the status of this ?

[ryanb945]

Any status update on this?

[hostep]

Is this related to #23077 & #23294?

• If yes, then it was fixed by eec9c26 (my guess is it will be included in Magento 2.3.4, but don't take my word for it)
• If no, then ignore me :)

[ryanb945]

It was related to #22161. Was that moved to those two ticket numbers you referenced?

[ryanb945]

Any update on this??

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[magento-engcom-team]

Hi @jbrada.

Thank you for your report and collaboration!

The related internal Jira ticket MC-24407 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.

[pmsteil]

Any details on what causes this "backlog" on the indexes?

Is there a workaround? I am seeing:

| catalogrule_product | Catalog Product Rule | Ready | Schedule | working (24658 in backlog)

[ryanb945]

Any details on what causes this "backlog" on the indexes?

Is there a workaround? I am seeing:

| catalogrule_product | Catalog Product Rule | Ready | Schedule | working (24658 in backlog)

From what I can tell, the cause is whenever there is a mass amount of data changed using the import function. Workaround that we use is to just run bin/magento indexer:reset and then running bin/magento indexer:reindex commands. That usually clears the backlog and makes all data updates show up properly on frontend. At least that is what works for us.