-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add configuration props for CQL PoolingOptions #776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
156b042 to
c425332
Compare
| configuration.get(REMOTE_CORE_CONNECTIONS_PER_HOST)) | ||
| .setConnectionsPerHost( | ||
| HostDistance.REMOTE, | ||
| configuration.get(LOCAL_MAX_CONNECTIONS_PER_HOST), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think REMOTE_CORE_CONNECTIONS_PER_HOST and LOCAL_MAX_CONNECTIONS_PER_HOST are switched.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. fixed. Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@robertdale Please review again.
09218e6 to
f382c3f
Compare
|
|
||
| ConfigOption<Integer> LOCAL_CORE_CONNECTIONS_PER_HOST = new ConfigOption<>( | ||
| CQL_NS, | ||
| "local-core-connection-per-host", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
local-core-connections-per-host? same for the others
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@analytically I fixed and updated my branch.
Make CQL PoolingOptions be configurable by adding the following new properties under `storage.cql` : - local-core-connection-per-host: The number of connections initially created and kept open to each host for local datacenter - local-max-connection-per-host: The maximum number of connections that can be created per host for local datacenter - local-max-request-per-connection: The maximum number of requests per connection for local datacenter - remote-core-connection-per-host: The number of connections initially created and kept open to each host for remote datacenter - remote-max-connection-per-host: The maximum number of connections that can be created per host for remote datacenter - remote-max-request-per-connection: The maximum number of requests per connection for remote datacenter Ref: related issue JanusGraph#775 Signed-off-by: Yihong Wang <yh.wang@ibm.com>
f382c3f to
b9a9f6d
Compare
Add configuration props for CQL PoolingOptions
| CQL_NS, | ||
| "local-core-connections-per-host", | ||
| "The number of connections initially created and kept open to each host for local datacenter", | ||
| ConfigOption.Type.FIXED, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any specific reason why this configuration is of type FIXED?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm asking because it does not seem clear to me why this could not be changed later on. Just asking to understand if there is some reason that I'm missing.
Add configuration props for CQL PoolingOptions
Make CQL PoolingOptions be configurable by adding the following new
properties under
storage.cql:The number of connections initially created and kept open to each host
for local datacenter
The maximum number of connections that can be created per host for
local datacenter
The maximum number of requests per connection for local datacenter
The number of connections initially created and kept open to each host
for remote datacenter
The maximum number of connections that can be created per host for
remote datacenter
The maximum number of requests per connection for remote datacenter
Ref: related issue #775
Signed-off-by: Yihong Wang yh.wang@ibm.com
Thank you for contributing to JanusGraph!
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
master)?For code changes:
Note:
Please ensure that once the PR is submitted, you check Travis CI for build issues and submit an update to your PR as soon as possible.