Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5725C184B8 for ; Tue, 6 Oct 2015 15:11:27 +0000 (UTC) Received: (qmail 61031 invoked by uid 500); 6 Oct 2015 15:11:27 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 61000 invoked by uid 500); 6 Oct 2015 15:11:27 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 60909 invoked by uid 99); 6 Oct 2015 15:11:27 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2015 15:11:27 +0000 Date: Tue, 6 Oct 2015 15:11:27 +0000 (UTC) From: "Philip Thompson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10445) Cassandra-stress throws max frame size error when SSL certification is enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945157#comment-14945157 ] Philip Thompson commented on CASSANDRA-10445: --------------------------------------------- If you compile and use the cassandra stress from trunk against your 2.1 cluster, does this still reproduce? > Cassandra-stress throws max frame size error when SSL certification is enabled > ------------------------------------------------------------------------------ > > Key: CASSANDRA-10445 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10445 > Project: Cassandra > Issue Type: Bug > Reporter: Sam Goldberg > Fix For: 2.1.x > > > Running cassandra-stress when SSL is enabled gives the following error and does not finish executing: > {quote} > cassandra-stress write n=1000000 > Exception in thread "main" java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: Frame size (352518912) larger than max length (15728640)! > at org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:144) > at org.apache.cassandra.stress.settings.StressSettings.getRawThriftClient(StressSettings.java:110) > at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpacesThrift(SettingsSchema.java:111) > at org.apache.cassandra.stress.settings.SettingsSchema.createKeySpaces(SettingsSchema.java:59) > at org.apache.cassandra.stress.settings.StressSettings.maybeCreateKeyspaces(StressSettings.java:205) > at org.apache.cassandra.stress.StressAction.run(StressAction.java:55) > at org.apache.cassandra.stress.Stress.main(Stress.java:109) > {quote} > I was able to reproduce this issue consistently via the following steps: > 1) Spin up 3 node cassandra cluster running 2.1.8 > 2) Perform cassandra-stress write n=1000000 > 3) Everything works! > 4) Generate keystore and truststore for each node in the cluster and distribute appropriately > 5) Modify cassandra.yaml on each node to enable SSL: > client_encryption_options: > enabled: true > keystore: / > # require_client_auth: false > # Set trustore and truststore_password if require_client_auth is true > truststore: / > truststore_password: > # More advanced defaults below: > protocol: ssl > 6) Restart each node. > 7) Perform cassandra-stress write n=1000000 > 8) Get Frame Size error, cassandra-stress fails > This may be related to CASSANDRA-9325. -- This message was sent by Atlassian JIRA (v6.3.4#6332)