search

scylladb / scylladb-cloud-doc-issues

A repo for Scylla Cloud docs issues
https://cloud.docs.scylladb.com/stable/
1 stars 1 forks source link

docs: Issue in page ScyllaDB Cloud FAQ #5

Open noellymedina opened 1 year ago

noellymedina commented 1 year ago

I would like to add more info in page https://cloud.docs.scylladb.com/master/getting-help/FAQ Session How can I enable DNS names for my cluster nodes?

Problem

Where it is:

Using DNS names eliminates the need to update the IP in the connection strings when there’s a change in the cluster, for example, when a node is replaced. In such cases, the node’s DNS name remains unchanged, sparing you the time and effort to update your application and drivers.

Suggest a fix

I would add:

Using DNS names eliminates the need to update the IP in the connection strings when there’s a change in the cluster, for example, when a node is replaced. In such cases, the node’s DNS name remains unchanged, sparing you the time and effort to update your application and drivers. The exception is when all the existing nodes of a cluster are replaced, which causes all IP addresses to change, so the driver should be recycled in order to refresh the IPs pointing to the DNS entries.

cc @annastuchlik

noellymedina commented 1 year ago

Clarifying when it is needed and when it's not:

It == updating their connection string with the correct and up to date access points and/or restarting their client-app to re-fetch the new IPs from the DNS.

It will not be needed when adding/removing (scale-out/in), as we do not touch the current nodes which their IPs are used for the DNS.

It will be needed if a node that was part of the IPs in the DNS, needed to be replaced (HW issue , Cloud vendor notifying re node to be decomm. etc.)

It will be needed in case of a scale-up/down, in which ALL nodes are being "replaced" by a new set of nodes (different instance type/size).

tzach commented 1 year ago

It will be needed in case of a scale-up/down, in which ALL nodes are being "replaced" by a new set of nodes (different instance type/size).

Repalcing a node can be a result of scaling out then scaling down, so I sugget to add a note on the scaling page as well. In any case, we should hide the option of using direct IPs

annastuchlik commented 1 year ago

@noellymedina Thanks for opening this issue. If I understand correctly, the information is relevant not only to the users manually enabling the DNS feature but to all Cloud users. If that's the case, we should update the Scaling page and refer to it from FAQ.

Some questions before I make the update:

d-helios commented 1 year ago

caching can happened at 

we need to provide exact examples how to disable cache or set it to lower numbers. our dns records have TTL=10

annastuchlik commented 1 year ago

@noellymedina @d-helios Can you add the examples to this issue or let me know who could?

annastuchlik commented 1 year ago

@d-helios @gmizrahi Could you advise? Who could help me document the ways to disable/limit cache on different levels?

dorlaor commented 1 year ago

We also need to explicitly write that the customer should NOT use IP addresses directly

d-helios commented 1 year ago

@annastuchlik right we discussing this issue in mail thread.

we need to understand:

after that we will back with update

annastuchlik commented 1 year ago

@d-helios Is there any update on this?

d-helios commented 1 year ago

here is summary about the current situation with drivers https://github.com/scylladb/scylla-drivers/issues/9 better to ask QA or somebody who tests this driver to provide recommended settings for each of them

cc: @mykaul

annastuchlik commented 1 year ago

@roydahan Could you assign a QA engineer to this issue? I can update the docs, but I need the input.

roydahan commented 1 year ago

@roydahan Could you assign a QA engineer to this issue?

I can update the docs, but I need the input.

I think that @avelanarius will be more helpful here, since he was assigned to the issue mentioned above and QA were not involved with this.

We still don't have these tests with DNS.

annastuchlik commented 6 months ago

@avelanarius ping