Skip to content
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

Added Dwellir RPC endpoints for Kusama and Polkadot relay chains #6024

Merged
merged 1 commit into from
Sep 6, 2021

Conversation

Maharacha
Copy link
Contributor

Dwellir runs RPC nodes for both Polkadot and Kusama relay chains. We want to contribute by making them public available!

Copy link
Member

@jacogr jacogr left a comment

Choose a reason for hiding this comment

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

Prefer to stay away from non-ascii

Copy link
Member

@jacogr jacogr left a comment

Choose a reason for hiding this comment

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

What monitoring do you have in-place?

I have had issues in the past with providers not being able to keep the infrastructure available, which ended up creating a support nightmare for me. Since these are really high-traffic chains, it needs to be handled appropriately.

(Endpoints are randomly selected for users, so when issues do happen it does create slight issues on my support queue)

@Maharacha
Copy link
Contributor Author

What monitoring do you have in-place?

I have had issues in the past with providers not being able to keep the infrastructure available, which ended up creating a support nightmare for me. Since these are really high-traffic chains, it needs to be handled appropriately.

(Endpoints are randomly selected for users, so when issues do happen it does create slight issues on my support queue)

To monitor the system resources, we use Grafana. We also have external monitoring that monitors all our services on our sites. For notifications on our alarms we use PagerDuty. Regarding availability, we have three sites located at different places in Sweden, where we can move our services between.

Can you give us a hint on how the much the traffic will be when we are added?

@jacogr
Copy link
Member

jacogr commented Aug 31, 2021

Honestly don’t know about the load - I don’t have access to infrastructure to check. But since endpoints gets selected randomly, you can more-or-less expect 1/N of all connections to your services. (Where N is the number of providers available)

@Maharacha
Copy link
Contributor Author

We have updated the name now. We have also changed to standard web ports. Ready to merge from our side!

@erik78se
Copy link

erik78se commented Sep 1, 2021

As a followup on your question about monitoring, we perform service monitoring remotely, performing a remote rpc call and an alarm is triggered if it takes more than 5 seconds to get a valid result.

We are going to implement automated failover for the service using some GSLB which will require no actions from your side.

@jacogr jacogr merged commit d734ec0 into polkadot-js:master Sep 6, 2021
@Maharacha
Copy link
Contributor Author

@jacogr We are writing Treasury Proposals for Kusama and Polkadot RPC. We have now been told that we should wait with merging until the proposal is approved. And that we should do two separate PR's, one for Kusama and one for Polkadot, since there will be two different proposals. Can you revert this and I will create new PR's?

@jacogr jacogr mentioned this pull request Sep 6, 2021
@rrtti
Copy link

rrtti commented Sep 7, 2021

Its fine if its merged on Kusama: the proposal will be for Kusama for now, the team cna show the nodes are already running and focus the efforts on the improvements they want to achieve for the service - as you prefer.

@polkadot-js-bot
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Sep 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants