cancel
Showing results for 
Search instead for 
Did you mean: 

How to turn off un-necessary updates to hjmpTS and to modifiedTS

ravi_tavva
Explorer
0 Kudos

We have a customer who is using hybris 5.4.0.0. The issue is that Catalog Synchronization job is performing very poorly updating only 3 items/sec.

Few observations that we made when JDBC logging is turned on.

The following statement on product is getting executed for 53 times 208|master|150920-20:16:20:332|0 ms|statement|UPDATE products SET hjmpTS = ? ,modifiedTS=? WHERE PK = ? |UPDATE products SET hjmpTS = 1462 ,modifiedTS='2015-09-20 20:16:20.331' WHERE PK = 8796199387137

The following statement is getting execute for 10 times for each productfeature that exists for a given product

186|master|150920-20:14:38:753|1 ms|statement|UPDATE productfeatures SET hjmpTS = ? ,modifiedTS=? WHERE PK = ? |UPDATE productfeatures SET hjmpTS = 123 ,modifiedTS='2015-09-20 20:14:38.752' WHERE PK = 8798096491107

ravi_tavva
Explorer
0 Kudos

Tried the following properties without success.

catalog.sync.enable.transactions=true relation..markmodified=false

Former Member
0 Kudos

hjmpTS is for internal use for the persistent system, it is an update count relevant when simultaneous modifications are being run on the item.As far as I know modifiedTS is part of synchronization process.I don't think thats the problem for slow sync.

Accepted Solutions (0)

Answers (1)

Answers (1)

ravi_tavva
Explorer
0 Kudos

Thanks for your response .

This morning I tried with version 5.4.0.5 which seems to resolved the issue, where I don't see the excessive/un-necessary DB statement execution though I have not modified anything in the product/productfeature values.

Will update with more of my findings.

Former Member
0 Kudos

Hi Ravi,

Were you able to find the root cause of the query being fired and how it got fixed in newer version? I'm experiencing same issue for Discounts table. Thanks, Kumar

andyfletcher
Active Contributor
0 Kudos

https://jira.hybris.com/browse/ECP-595

It does seem strange that it was fixed with 5.4.0.5 since the ticket linked above says it was fixed for the 5.4 relase in 5.4.0.7