Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
pcmt
pcmt
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 146
    • Issues 146
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • pcmt
  • pcmtpcmt
  • Wiki
    • Development
  • Troubleshooting

Last edited by Mateusz Kowalewski Oct 30, 2019
Page history

Troubleshooting

Slow import process (w/ lots of variants)

If you will find the problem with long time during import products process, check process method in ProductProcessor. We override it and created ProductProcessor2 for PCMT_XLSX_PRODUCT_IMPORT job.

// HERE IS THE PROBLEM WITH LONG LOADING DATA
//    $violations = $this->validateProduct($product);
//
//    if ($violations->count() > 0) {
//      $this->detachProduct($product);
//      $this->skipItemWithConstraintViolations($item, $violations);
//    }
// END HERE IS THE PROBLEM WITH LONG LOADING DATA

Out of memory error in import

  • That to avoid the previous memory issues, we can change the the # of products processed in batches during import (e.g. default is 100, so we could bump it down to 10). You need to override pim_job_product_batch_size parameter which declaration you can find in vendor/akeneo/pim-community-dev/src/Akeneo/Platform/config/pim.yml

ElasticSearch rise Errors::Forbidden: [403] {"error":{"root_cause":[{"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"}

This happens because ElasticSearch is supervising total allocated disk space. Sometimes it may cause unexpected errors. When ES detects low disk space (even if it isn't low though) it switches into flood mode and prevents from further indexing. If freeing up space doesn't help, change settings on ES instance, by issuing:

curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_cluster/settings -d '{ "transient": { "cluster.routing.allocation.disk.threshold_enabled": false } }'

curl -XPUT -H "Content-Type: application/json" http://localhost:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

if the Response is: {"acknowledged":true,"persistent":{},"transient":{"cluster":{"routing":{"allocation":{"disk":{"threshold_enabled":"false"}}}}}}

then try to run process (i.e indexing) again.

Clone repository
  • Akeneo design elements
  • Architecture
  • Contributors
  • Development
    • Akeneo Import and Export Jobs structure
    • Code style
    • Git flow Git working methodology
    • How to create Jobs
    • How to create permission
    • PHPUnit settings step by step
    • Troubleshooting
    • Xdebug settings step by step
  • Functional and Behavior Tests in PCMT (Behat & Selenium)
  • How to Version and Release
  • Request Access
  • Test Cases
View All Pages