Magento產品價格重新索引掛在DELETE查詢

當我從SSH運行它時，我的Magento Enterprise 1.13安裝的價格重新索引不再完成。所有其他指標都很好。我離開它最長的時間是4天。Magento產品價格重新索引掛在DELETE查詢

服務器規格：

6芯
15GB RAM
200GB HDD
CentOS 6的

我可以使用請參閱「SHOW PROCESSLIST;」

DELETE `index_price` FROM `catalog_product_index_price` AS `index_price` LEFT JOIN `catalog_product_index_price_idx` AS `ip_tmp` ON index_price.entity_id = ip_tmp.entity_id AND index_price.website_id = ip_tmp.website_id WHERE (ip_tmp.entity_id IS NULL)

我檢查了兩個表的屬性（在此查詢正在運行）：

catalog_product_index_price = 16437361行，InnoDB類型，它與此查詢「發送數據」的狀態掛起大小2.4GB
catalog_product_index_price_idx = 16314589行，鍵入INNODB和大小2.1GB

下面是表結構和索引：

CREATE TABLE IF NOT EXISTS `catalog_product_index_price` (
    `entity_id` int(10) unsigned NOT NULL COMMENT 'Entity ID', 
    `customer_group_id` smallint(5) unsigned NOT NULL COMMENT 'Customer Group ID', 
    `website_id` smallint(5) unsigned NOT NULL COMMENT 'Website ID', 
    `tax_class_id` smallint(5) unsigned DEFAULT '0' COMMENT 'Tax Class ID', 
    `price` decimal(12,4) DEFAULT NULL COMMENT 'Price', 
    `final_price` decimal(12,4) DEFAULT NULL COMMENT 'Final Price', 
    `min_price` decimal(12,4) DEFAULT NULL COMMENT 'Min Price', 
    `max_price` decimal(12,4) DEFAULT NULL COMMENT 'Max Price', 
    `tier_price` decimal(12,4) DEFAULT NULL COMMENT 'Tier Price', 
    `group_price` decimal(12,4) DEFAULT NULL COMMENT 'Group price' 
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Catalog Product Price Index Table'; 

ALTER TABLE `catalog_product_index_price` 
ADD PRIMARY KEY (`entity_id`,`customer_group_id`,`website_id`), ADD KEY `IDX_CATALOG_PRODUCT_INDEX_PRICE_CUSTOMER_GROUP_ID` (`customer_group_id`), ADD KEY `IDX_CATALOG_PRODUCT_INDEX_PRICE_WEBSITE_ID` (`website_id`), ADD KEY `IDX_CATALOG_PRODUCT_INDEX_PRICE_MIN_PRICE` (`min_price`), ADD KEY `IDX_CAT_PRD_IDX_PRICE_WS_ID_CSTR_GROUP_ID_MIN_PRICE` (`website_id`,`customer_group_id`,`min_price`); 

CREATE TABLE IF NOT EXISTS `catalog_product_index_price_idx` (
    `entity_id` int(10) unsigned NOT NULL COMMENT 'Entity ID', 
    `customer_group_id` smallint(5) unsigned NOT NULL COMMENT 'Customer Group ID', 
    `website_id` smallint(5) unsigned NOT NULL COMMENT 'Website ID', 
    `tax_class_id` smallint(5) unsigned DEFAULT '0' COMMENT 'Tax Class ID', 
    `price` decimal(12,4) DEFAULT NULL COMMENT 'Price', 
    `final_price` decimal(12,4) DEFAULT NULL COMMENT 'Final Price', 
    `min_price` decimal(12,4) DEFAULT NULL COMMENT 'Min Price', 
    `max_price` decimal(12,4) DEFAULT NULL COMMENT 'Max Price', 
    `tier_price` decimal(12,4) DEFAULT NULL COMMENT 'Tier Price', 
    `group_price` decimal(12,4) DEFAULT NULL COMMENT 'Group price' 
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Catalog Product Price Indexer Index Table'; 

ALTER TABLE `catalog_product_index_price_idx` 
ADD PRIMARY KEY (`entity_id`,`customer_group_id`,`website_id`), ADD KEY `IDX_CATALOG_PRODUCT_INDEX_PRICE_IDX_CUSTOMER_GROUP_ID` (`customer_group_id`), ADD KEY `IDX_CATALOG_PRODUCT_INDEX_PRICE_IDX_WEBSITE_ID` (`website_id`), ADD KEY `IDX_CATALOG_PRODUCT_INDEX_PRICE_IDX_MIN_PRICE` (`min_price`);

我曾嘗試在兩個表上運行mysql命令「OPTIMIZE」，並運行檢查任何外鍵問題都沒有幫助。

我也嘗試更改my.cnf，因爲它已被建議可能已達到「innodb_lock_wait_timeout」限制。請看下文中我的my.cnf：

[mysqld] 
datadir=/var/lib/mysql 
socket=/var/lib/mysql/mysql.sock 
user=mysql 
symbolic-links=0 

thread_concurrency=12 
thread_cache_size=64 
#wait_timeout=600 
#wait_timeout=60 
#table_cache=2048 
table_cache=1024 
query_cache_type=1 
query_cache_size=1024M 
#query_cache_limit=16M 
query_cache_limit=32M 
key_buffer_size=256M 
max_allowed_packet=2048M 
#max_connections=1000 
max_connections=600 
tmp_table_size=1024M 
max_heap_table_size=1024M 
table_definition_cache=4000 
table_open_cache=4000 
#sort_buffer_size=1M 
#read_buffer_size=1M 
sort_buffer_size=8M 
read_buffer_size=4M 
join_buffer_size=16M 
#below files to help with crons 
#open_files_limit=131070 
wait_timeout=9000 
connect_timeout=9000 

innodb_thread_concurrency=12 
innodb_file_per_table=1 
#innodb_buffer_pool_size=4G 
#innodb_buffer_pool_size=3G 
innodb_buffer_pool_size=7G 
innodb_lock_wait_timeout=9000 
innodb_flush_log_at_trx_commit=1 
innodb_additional_mem_pool_size=24M 
#innodb_fast_shutdown=0 
innodb_log_buffer_size=8M 
innodb_log_file_size=128M 

#log_error=/var/log/mysql/mysql-error.log 
#log_queries_not_using_indexes=1 
#slow_query_log_file=/var/log/mysql/mysql-slow.log 
#log_slow_queries=ON

來源

2014-10-20 ncheese

我用表的完整主鍵修改產品再編索引，以刪除「catalog_product_index_price」表中產品的價格條目固定這一點。要做到這一點，你需要重寫這個文件：/app/code/core/Enterprise/Catalog/Model/Index/Action/Product/Price/Abstract.php和改變

$select = $this->_connection->select() 
     ->from(array('index_price' => $this->_getTable('catalog/product_index_price')), null) 
     ->joinLeft(
      array('ip_tmp' => $this->_getIdxTable()), 
      'index_price.entity_id = ip_tmp.entity_id AND index_price.website_id = ip_tmp.website_id', 
      array() 
     ) 
     ->where('ip_tmp.entity_id IS NULL');

到...

$select = $this->_connection->select() 
     ->from(array('index_price' => $this->_getTable('catalog/product_index_price')), null) 
     ->joinLeft(
      array('ip_tmp' => $this->_getIdxTable()), 
      'index_price.entity_id = ip_tmp.entity_id AND index_price.website_id = ip_tmp.website_id AND index_price.customer_group_id = ip_tmp.customer_group_id', 
      array() 
     ) 
     ->where('ip_tmp.entity_id IS NULL');

做到這一點你自己的危險，到目前爲止一切似乎沒問題。我可以看到的唯一不足之處是可能會在「catalog_product_index_price」表中留下一些冗餘行。除此之外，我沒有任何問題。

來源

2014-12-10 17:26:53 ncheese

Magento產品價格重新索引掛在DELETE查詢

回答

相關問題