cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9601) Allow an initial connection timeout to be set in cqlsh
Date Thu, 09 Jul 2015 01:38:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619719#comment-14619719
] 

Stefania commented on CASSANDRA-9601:
-------------------------------------

Thanks for backporting Tyler! CI looks OK but I've launched a second dtest job to shake one
flaky test (thrift_hsha_test.ThriftHSHATest.test_closing_connections).

I've reviewed the backport, it looks good. 

I've run {{cqlsh_tests/cqlsh_tests.py:TestCqlsh.test_connect_timeout}} locally as it is currently
skipped by Jenkins due to the 2.2 since tag and it passed on my box. 

Once this is committed we mustn't forget to change the since tag in the dtest.

> Allow an initial connection timeout to be set in cqlsh
> ------------------------------------------------------
>
>                 Key: CASSANDRA-9601
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9601
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Mike Adamson
>            Assignee: Stefania
>              Labels: cqlsh
>             Fix For: 2.2.0 rc2
>
>
> [PYTHON-206|https://datastax-oss.atlassian.net/browse/PYTHON-206] introduced the ability
to change the initial connection timeout on connections from the default of 5s.
> This change was introduced because some auth providers (kerberos) can take longer than
5s to complete a first time negotiation for a connection. 
> cqlsh should allow this setting to be changed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message