You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Oleg Zhovtanyuk (Jira)" <ji...@apache.org> on 2022/01/17 12:18:00 UTC
[jira] [Updated] (CASSANDRA-17263) sstableloader ignores the storage port option
[ https://issues.apache.org/jira/browse/CASSANDRA-17263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Zhovtanyuk updated CASSANDRA-17263:
----------------------------------------
Description:
sstableloader silently ignores the storage port option and connects to the storage port of the server.
E.g.
{code:java}
sstableloader -v -d 192.168.1.24 -p 32181 -sp 32182 -u USER -pw PASSWORD backups/test-workspace/test-table-9150b730742911ec9d011fb0ef4f5206 {code}
Here sstableloader will ignore the storage port 32182 and try to connect to port 7000, if the server reports itself listening on port 7000.
This seems natural (servers listens on port 7000 so just use it), but it does not work, when Cassandra runs in a Docker container, started via an orchestrator (Kubernetes, Mesos) with ports mapped.
E.g.
{code:java}
docker run -it \
-p 32181:9042 \
-p 32182:7000 \
cassandra:4.0.1{code}
Here the storage port will be 7000 _inside_ the container (and Cassandra server exposes it), but outside the container the port is 32182.
The code ({*}NativeSSTableLoaderClient{*} - {*}{*}[link|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/utils/NativeSSTableLoaderClient.java#L83])
{code:java}
Set<Host> endpoints = metadata.getReplicas(Metadata.quote(keyspace), tokenRange);
...
for (Host endpoint : endpoints)
{
int broadcastPort = endpoint.getBroadcastSocketAddress().getPort();
// use port from broadcast address if set.
int portToUse = broadcastPort != 0 ? broadcastPort : storagePort;
... {code}
It effectively ignores the {*}storagePort{*}, taken from CLI option. I believe, CLI option should have a priority here - let the user to decide what he wants.
was:
sstableloader silently ignores the native port option and connects to default port.
E.g.
{code:java}
sstableloader -v -d 192.168.1.24 -p 32181 -sp 32182 -u USER -pw PASSWORD backups/test-workspace/test-table-9150b730742911ec9d011fb0ef4f5206 {code}
fails with
{code:java}
All host(s) tried for query failed (tried: /192.168.1.24:9042 (com.datastax.driver.core.exceptions.TransportException: [/192.168.1.24:9042] Cannot connect))com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /192.168.1.24:9042 (com.datastax.driver.core.exceptions.TransportException: [/192.168.1.24:9042] Cannot connect)) at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:270) at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:109) at com.datastax.driver.core.Cluster$Manager.negotiateProtocolVersionAndConnect(Cluster.java:1813) at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1726) at com.datastax.driver.core.Cluster.init(Cluster.java:214) at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:387) at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:366) at com.datastax.driver.core.Cluster.connect(Cluster.java:311) at org.apache.cassandra.utils.NativeSSTableLoaderClient.init(NativeSSTableLoaderClient.java:75) at org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:183) at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:83) at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:51)Exception in thread "main" org.apache.cassandra.tools.BulkLoadException: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /192.168.1.24:9042 (com.datastax.driver.core.exceptions.TransportException: [/192.168.1.24:9042] Cannot connect)) at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:96) at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:51)Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /192.168.1.24:9042 (com.datastax.driver.core.exceptions.TransportException: [/192.168.1.24:9042] Cannot connect)) at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:270) at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:109) at com.datastax.driver.core.Cluster$Manager.negotiateProtocolVersionAndConnect(Cluster.java:1813) at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1726) at com.datastax.driver.core.Cluster.init(Cluster.java:214) at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:387) at com.datastax.driver.core.Cluster.connectAsync(Cluster.java:366) at com.datastax.driver.core.Cluster.connect(Cluster.java:311) at org.apache.cassandra.utils.NativeSSTableLoaderClient.init(NativeSSTableLoaderClient.java:75) at org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:183) at org.apache.cassandra.tools.BulkLoader.load(BulkLoader.java:83) ... 1 more
{code}
The solution is to pass '-d HOST:PORT', but it requires digging in the source code and it not documented.
> sstableloader ignores the storage port option
> ---------------------------------------------
>
> Key: CASSANDRA-17263
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17263
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
> Reporter: Oleg Zhovtanyuk
> Priority: Normal
>
> sstableloader silently ignores the storage port option and connects to the storage port of the server.
> E.g.
> {code:java}
> sstableloader -v -d 192.168.1.24 -p 32181 -sp 32182 -u USER -pw PASSWORD backups/test-workspace/test-table-9150b730742911ec9d011fb0ef4f5206 {code}
> Here sstableloader will ignore the storage port 32182 and try to connect to port 7000, if the server reports itself listening on port 7000.
>
> This seems natural (servers listens on port 7000 so just use it), but it does not work, when Cassandra runs in a Docker container, started via an orchestrator (Kubernetes, Mesos) with ports mapped.
> E.g.
>
> {code:java}
> docker run -it \
> -p 32181:9042 \
> -p 32182:7000 \
> cassandra:4.0.1{code}
>
> Here the storage port will be 7000 _inside_ the container (and Cassandra server exposes it), but outside the container the port is 32182.
>
> The code ({*}NativeSSTableLoaderClient{*} - {*}{*}[link|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/utils/NativeSSTableLoaderClient.java#L83])
> {code:java}
> Set<Host> endpoints = metadata.getReplicas(Metadata.quote(keyspace), tokenRange);
> ...
> for (Host endpoint : endpoints)
> {
> int broadcastPort = endpoint.getBroadcastSocketAddress().getPort();
> // use port from broadcast address if set.
> int portToUse = broadcastPort != 0 ? broadcastPort : storagePort;
> ... {code}
> It effectively ignores the {*}storagePort{*}, taken from CLI option. I believe, CLI option should have a priority here - let the user to decide what he wants.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org