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
Copy file name to clipboardExpand all lines: docs/flex/interactive/configuration.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Below is a list of all configurable items:
15
15
| admin-port | 7777 | The port of the interactive admin service | v0.3 |
16
16
| storedproc-port | 10000 | The port of the interactive stored procedure service | v0.3 |
17
17
| cypher-port | 7687 | The port of the cypher service | v0.3 |
18
-
| config | None | The customized configuration file for engine interactive service | v0.4 |
18
+
| config | None | The customized configuration file for engine interactive service | v0.4 |
19
19
<!-- | gremlin-port | None | The port of the gremlin service | v0.3 | -->
20
20
21
21
@@ -50,7 +50,7 @@ By default, `Interactive` will initialize the service with its default settings.
50
50
However, GraphScope Interactive is designed to be flexible and adaptable to your specific needs. This means you can tailor the service's behavior using custom configurations.
51
51
52
52
53
-
#### Customizing Your Service Configuration
53
+
#### Customizing Interactive Engine Service Configuration
54
54
To customize the service's settings, you can provide a YAML configuration file `interactive_config.yaml`. This file allows you to specify various parameters, from directory paths to log levels, ensuring the service aligns with your requirements. To use a custom configuration, simply pass the YAML file to the command as follows:
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).
64
77
65
78
66
79
##### Sample Configuration
@@ -121,6 +134,7 @@ In this following table, we use the `.` notation to represent the hierarchy with
121
134
| compiler.planner.rules.NotMatchToAntiJoinRule | N/A | An optimization rule that transforms a "not exist" pattern into an anti-join operation | 0.0.1 |
122
135
| compiler.query_timeout | 3000000 | The maximum time for compiler to wait engine's reply, in `ms` | 0.0.3 |
123
136
| 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 |
0 commit comments