[
https://issues.apache.org/jira/browse/CASSANDRA-17210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17210:
------------------------------------------
Test and Documentation Plan: manual testing
Status: Patch Available (was: In Progress)
The problem is that native port is resolved after hosts are and default port is
9042 so there is no chance that hosts resoluion would use native port from the
configuration because its parsing is done after hosts are configured. Simple
movement of native port resolution solves the issue.
https://github.com/apache/cassandra/pull/1507
> Not able to override default transport port in cassandra 4.0
> ------------------------------------------------------------
>
> Key: CASSANDRA-17210
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17210
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
> Reporter: NISHANT GUPTA
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.1, 4.0.4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Bulk Loader is not honouring "-p" option given on the command line of the
> sstableloader.
> The command line used is:
> ~/apache-cassandra-4.0.1/bin/sstableloader -d 10.14.20.148 -cph 1 -idct 0 -p
> 9942 -ssp 7011 -sp 7010 --verbose ~/cassandra4_experiment/nishant/employee/
>
> but the call is still going to /10.14.20.148:9042. We are just passing the
> host information to the Cluster.Builder in NativeSSTableLoaderClient.java:
> Cluster.Builder builder =
> Cluster.builder().addContactPointsWithPorts(hosts).allowBetaProtocolVersion();
> Looks like default port is getting picked inside
> com.datastax.driver.core.cluster.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
