Skip to content

[IOTDB-2754] SessionPool auto redirect IoTDB instance#5267

Merged
qiaojialin merged 5 commits intoapache:masterfrom
CRZbulabula:SessionPool_auto_redirect
Mar 18, 2022
Merged

[IOTDB-2754] SessionPool auto redirect IoTDB instance#5267
qiaojialin merged 5 commits intoapache:masterfrom
CRZbulabula:SessionPool_auto_redirect

Conversation

@CRZbulabula
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Mar 17, 2022

Coverage Status

Coverage decreased (-0.003%) to 65.441% when pulling 6754aef on CRZbulabula:SessionPool_auto_redirect into 3deadae on apache:master.

Copy link
Contributor

@SilverNarcissus SilverNarcissus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! We also need some test for this new session pool, could you please add some IT?

Copy link
Contributor

@OneSizeFitsQuorum OneSizeFitsQuorum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Only minor issue. PTAL

Copy link
Contributor

@OneSizeFitsQuorum OneSizeFitsQuorum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PTAL

Config.DEFAULT_CONNECTION_TIMEOUT_MS);
}

public SessionPool(List<String> nodeUrls, String user, String password, int maxSize) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update the sessionPool documentation to show greater fault tolerance when passing multiple endpoints like a session

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@CRZbulabula
Copy link
Contributor Author

Nice work! We also need some test for this new session pool, could you please add some IT?

Sorry, I can't add IT for this new feature. Because our IT environment only supports to run a single IoTDB Instance. In fact, this example code acts as a test. You can start IoTDB-server either on port 6667 or on port 6668 and this example code still work.

Copy link
Contributor

@SilverNarcissus SilverNarcissus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look good to me~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants