You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please be aware that you're not required to configure every option. Simply adjust the settings that are relevant to your needs. Any options left unconfigured will automatically adopt their default values, as detailed in the following sections.
62
62
```
63
63
64
-
#### Customize Coordinator Service Configuration
65
-
66
-
When deploying Interactive, a supplementary service called the Coordinator is also initiated. This service functions similarly to the `ApiServer` in Kubernetes, providing users with a consistent and standardized set of APIs to interact with the GraphScope platform.
67
-
You could also customize the configuration for coordinator service, just put the configuration in `coordinator` section.
68
-
69
-
An example of a coordinator related configuration is as follows:
70
-
71
-
```yaml
72
-
coordinator:
73
-
max_content_length: 5242880# maximum bytes of content the coordinator can handle
74
-
```
75
-
76
-
For more details, consult [config.py](https://github.com/alibaba/GraphScope/blob/main/python/graphscope/config.py).
77
-
78
64
79
65
##### Sample Configuration
80
66
Here's a glimpse of what a typical YAML configuration file might look like:
@@ -134,7 +120,7 @@ In this following table, we use the `.` notation to represent the hierarchy with
134
120
| compiler.planner.rules.NotMatchToAntiJoinRule | N/A | An optimization rule that transforms a "not exist" pattern into an anti-join operation | 0.0.1 |
135
121
| compiler.query_timeout | 3000000 | The maximum time for compiler to wait engine's reply, in `ms` | 0.0.3 |
136
122
| http_service.sharding_mode | exclusive | The sharding mode for http service, In exclusive mode, one shard is reserved exclusively for service admin request. In cooperative, both query request and admin request could be served by any shard. | 0.5 |
137
-
| coordinator.max_content_length | 1073741824 | The maximum length of a http request that coordinator could handle | 0.5 |
123
+
| http_service.max_content_length | 1GB | The maximum length of a http request that admin http service could handle | 0.5 |
0 commit comments