创建session修改参数报错 #344
-
Graphscope默认参数创建session时出现内存不够的异常,修改参数后报如下错,貌似不支持参数修改? graphscope.set_option(k8s_coordinator_mem="2Gi") Initializing graphscope session with parameters: {'addr': None, 'cluster_type': 'k8s', 'num_workers': 2, 'preemptive': True, 'k8s_namespace': None, 'k8s_service_type': 'NodePort', 'k8s_gs_image': 'registry.cn-hongkong.aliyuncs.com/graphscope/graphscope:0.4.0', 'k8s_etcd_image': 'quay.io/coreos/etcd:v3.4.13', 'k8s_image_pull_policy': 'IfNotPresent', 'k8s_image_pull_secrets': [], 'k8s_gie_graph_manager_image': 'registry.cn-hongkong.aliyuncs.com/graphscope/maxgraph_standalone_manager:0.4.0', 'k8s_zookeeper_image': 'zookeeper:3.4.14', 'k8s_coordinator_cpu': 1.0, 'k8s_coordinator_mem': '2Gi', 'k8s_etcd_num_pods': 3, 'k8s_etcd_cpu': 0.5, 'k8s_etcd_mem': '128Mi', 'k8s_zookeeper_cpu': 0.5, 'k8s_zookeeper_mem': '256Mi', 'k8s_gie_graph_manager_cpu': 1.0, 'k8s_gie_graph_manager_mem': '4Gi', 'k8s_vineyard_daemonset': '', 'k8s_vineyard_cpu': 0.5, 'k8s_vineyard_mem': '512Mi', 'vineyard_shared_mem': '4Gi', 'k8s_engine_cpu': 0.5, 'k8s_engine_mem': '4Gi', 'k8s_mars_worker_cpu': 0.5, 'k8s_mars_worker_mem': '4Gi', 'k8s_mars_scheduler_cpu': 0.5, 'k8s_mars_scheduler_mem': '2Gi', 'with_mars': False, 'k8s_volumes': {}, 'k8s_waiting_for_delete': False, 'timeout_seconds': 600, 'dangling_timeout_seconds': 600, 'k8s_client_config': {}}
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi, @bitao666, thank you for posting this question in the discussions, and welcome to the GraphScope discussions. From your log, the exception In your current version of GraphScope, the coordinator memory requests defaults to '4Gi'. So your parameters graphscope.set_option(k8s_coordinator_mem="2Gi", preemptive=False)
s=graphscope.session()
|
Beta Was this translation helpful? Give feedback.
Hi, @bitao666, thank you for posting this question in the discussions, and welcome to the GraphScope discussions.
From your log, the exception
resources.requests: Invalid value: "4Gi": must be less than or equal to memory limit'.
occurs when resource limits less than requests.In your current version of GraphScope, the coordinator memory requests defaults to '4Gi'. So your parameters
k8s_coordinator_mem="2Gi"
cannot pass the API check. You can solve this problem by passingpreemptive=False
together.From GraphScope Doc