alibaba/GraphScope

[BUG] Performance degradation when worker scales in small datasets.

Open

#2,834 opened on Jun 7, 2023

View on GitHub
 (14 comments) (0 reactions) (0 assignees)HTML (2,401 stars) (301 forks)batch import
bugcomponent:gaecomponent:pythongood first issue

Description

Describe the bug We tested page_rank on datagen-7_5-fb.e dataset using graphscope:0.21.0 k8s mode, but it failed in add_edegs.

To Reproduce Steps to reproduce the behavior:

  1. create session using k8s mode
  2. read the dataset
  3. create graph using 'add_edges'
  4. failed in 'add_edges'

Expected behavior create graph successful.

Screenshots We found the logs in coordinator pod in k8s. During 'add_edges', the logs show that craete engine headless services .. ... ... kubernetes.client.exceptions.ApiException:(409) Reson:Conflict ..... services 'gs-engine-onmitz-headless' already exists.

At last, coordinator pod did not work.

Environment (please complete the following information):

  • GraphScope version: [0.21.0]
  • OS: [Ubuntu 20.04]
  • Kubernetes Version [v1.21.4]

Additional context We tested dataset 'twitter.e' on k8s mode, all is ok. We tested dataset 'datagen-7_5-fb.e' on hosts mode, all is ok. Maybe big dataset didnot work on k8s mode? (graphscope 0.21.0)

Contributor guide

Tech stack
pythonkubernetes
Domain
clouddevopsperformance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic knowledge of Kubernetesfamiliarity with GraphScope
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the Kubernetes conflict error 'gs engine onmitz headless' already exists. Check the coordinator pod logs for sequence of service creation. Look at the GraphScope helm chart or deployment scripts to understand how headless services are created and why they might conflict. Consider if dataset size affects service naming or lifecycle. Examine the add edges function in the codebase for any resource management issues.
[BUG] Performance degradation when worker scales in small datasets. · alibaba/GraphScope#2834 | Good First Issue