[
https://issues.apache.org/jira/browse/CASSANDRA-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111295#comment-18111295
]
Nivy Kani edited comment on CASSANDRA-21539 at 9/3/26 9:49 PM:
---------------------------------------------------------------
That makes sense to me; using `getHostString()` and reverting the column
removal sounds safer while still addressing the original ticket. I'll also add
a NEWS.txt entry mentioning that the `hostname` column will no longer resolve
to an address to avoid overwhelming DNS.
I'm preparing the 4.0, 4.1, 5.0, 6.0, and trunk patches now and will link them
here soon.
was (Author: JIRAUSER311854):
That makes sense to me; using `getHostString()` and reverting the column
removal sounds safer while still addressing the original ticket. I'll also add
a NEWS.txt entry mentioning that the `hostname` column will no longer resolve
to an address to avoid overwhelming DNS.
I'm preparing the 4.0, 5.0, and 6.0, and trunk patches now and will link them
here soon.
> Querying system_views.clients causes a DNS lookup for each unique connected
> client address
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-21539
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21539
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Feature/Virtual Tables
> Reporter: Nivy Kani
> Assignee: Nivy Kani
> Priority: Normal
> Fix For: 4.0.22, 4.1.13, 5.0.10, 6.0-alpha3, 7.0
>
> Attachments: 4.0-ci_summary.html, 4.0-result_details.tar.gz.zip,
> 5.0-ci_summary.html, 5.0-result_details.tar.gz, 6.0-ci_summary.html,
> 6.0-result_details.tar.gz, ci_summary-1.html, ci_summary.html,
> result_details.tar-1.gz, result_details.tar.gz
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> It looks like queries to the system_views.clients table does a DNS lookup for
> each unique address:
> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/virtual/ClientsTable.java#L91
>
> Given Java's internal DNS caches, this is really only potentially slow on the
> first query, but we should avoid doing DNS lookups here as a workflow that
> queries this table on each node to collect client information could
> potentially overwhelm DNS this way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
