mesh icon indicating copy to clipboard operation
mesh copied to clipboard

/Sync doesn't populate nodes in elasticsearch

Open DavidOrtizR opened this issue 4 years ago • 3 comments

Gentics Mesh Version, operating system, or hardware.

  • v1.7.6
  • v1.7.9

Operating System

  • K8s

Elasticsearch 7.7.0

Problem

/search/sync doesn't work properly.

Reproducer

1.-Create a new export file using the API /admin/graphdb/export 2.- Import using /admin/graphdb/import 3.- Clear indexes /search/clear 4.- Sync indexes using /search/sync

Expected behaviour

After restoring a backup or importing an export file and clear (/search/clear) and sync (/search/sync), the indexes in elasticseach should be populated as before.

Actual behaviour

After restoring a backup or importing an export file and clear (/search/clear) and sync (/search/sync), the indexes in elasticseach are empty

DavidOrtizR avatar May 19 '21 12:05 DavidOrtizR

Hi @plyhun, any updates on this topic?

DavidOrtizR avatar Aug 03 '21 09:08 DavidOrtizR

Hi @DavidOrtizR , I have just checked the described behavior at the following environment:

  1. export at Mesh 1.6.16, import at clean Mesh 1.7.14
  2. export at Mesh 1.7.14, clean it by deleting the graphdb folder, import back at 1.7.14.

Both usecases reported the same results:

{
  "available": true,
  "metrics": {
    "tagfamily": {
      "insert": {
        "synced": 6,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 0,
        "pending": 0
      }
    },
    "schema": {
      "insert": {
        "synced": 17,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 3,
        "pending": 0
      }
    },
    "node": {
      "insert": {
        "synced": 4235,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 0,
        "pending": 0
      }
    },
    "role": {
      "insert": {
        "synced": 4,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 2,
        "pending": 0
      }
    },
    "microschema": {
      "insert": {
        "synced": 1,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 0,
        "pending": 0
      }
    },
    "project": {
      "insert": {
        "synced": 2,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 0,
        "pending": 0
      }
    },
    "tag": {
      "insert": {
        "synced": 2,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 0,
        "pending": 0
      }
    },
    "user": {
      "insert": {
        "synced": 1214,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 2,
        "pending": 0
      }
    },
    "group": {
      "insert": {
        "synced": 5,
        "pending": 0
      },
      "update": {
        "synced": 0,
        "pending": 0
      },
      "delete": {
        "synced": 2,
        "pending": 0
      }
    }
  }
}

e.g. the schemas and nodes have been synced. Couldn't you please try with the latest v1.7.14, and monitor the logs during the backup/restore/index sync? Thanks in advance!

plyhun avatar Aug 16 '21 13:08 plyhun

Having the same issue here (v1.7.22).

danfabi avatar Jan 03 '22 19:01 danfabi