Skip to content

Unexpected exception during request - An existing connection was forcibly closed by the remote host #8

Closed
ananthonline opened this Issue Jan 11, 2013 · 32 comments

3 participants

@ananthonline

The following simple insert code causes Cassandra to throw this exception and terminate any clients currently connected to it. This causes subsequent reads of the table (Foo.Bar) to return

Command execution failed with error 'Unexpected read count'

Full sample code follows - note that this almost the same as your insert batch sample code except that it uses blobs instead of primitive types - it works fine for those:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading;
using System.Threading.Tasks;
using CassandraSharp;
using CassandraSharp.Config;
using CassandraSharp.CQL;
using CassandraSharp.CQLPoco;


namespace ConsoleApplication1
{
    class Program
    {
        private static long _running = 0;

        static void Main(string[] args)
        {
            XmlConfigurator.Configure();
            using (var cluster = ClusterManager.GetCluster("TestCluster"))
            {
                const string createKeyspaceFoo = "CREATE KEYSPACE Foo WITH replication = {'class': 'SimpleStrategy', 'replication_factor' : 1}";
                cluster.ExecuteNonQuery(createKeyspaceFoo, ConsistencyLevel.QUORUM)
                    .Wait();

                const string createBar = "CREATE TABLE Foo.Bar (id int, Baz blob, PRIMARY KEY (id))";
                cluster.ExecuteNonQuery(createBar, ConsistencyLevel.QUORUM)
                    .Wait();

                const string insertBatch = "INSERT INTO Foo.Bar (id, Baz) VALUES (?, ?)";
                var preparedInsert = cluster.Prepare(insertBatch).Result;

                const int Times = 100;
                const int BlobSize = 25000;

                var random = new Random();

                for (int i = 0; i < Times; i++)
                {
                    Interlocked.Increment(ref _running);
                    var data = (from idx in Enumerable.Range(0, BlobSize) select (byte)random.Next(byte.MaxValue)).ToArray();
                    // var data = (float)random.NextDouble();
                    preparedInsert.ExecuteNonQuery(ConsistencyLevel.ONE, new { id = i, Baz = data })
                        .ContinueWith(_ => Interlocked.Decrement(ref _running));
                }

                while (Thread.VolatileRead(ref _running) > 0)
                    Thread.Sleep(1000);
            }
            ClusterManager.Shutdown();
        }
    }
}
@hjarraya

When I try to run your code, I get a cast exception.
This is not due to data variable type is float, where in the schema is specified as int?

@pchalamet
Owner
@ananthonline

Sorry - that was a typo in the pasted code. Edited now to reproduce the error. The error happens when I use a blob datatype on Baz (the wrong code above was testing it with simple datatypes, which work fine)

When using blobs - there are no exceptions in my C# program.

'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\11.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\11.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\11.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Users\i51864\Documents\Visual Studio 2012\Projects\CassandraBlobInsertTest\CassandraBlobInsertTest\bin\Debug\CassandraBlobInsertTest.vshost.exe', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 'vshost.NotifyLoad' (0x3c9c) has exited with code 0 (0x0).
The thread '<No Name>' (0x353c) has exited with code 0 (0x0).
The thread 'vshost.LoadReference' (0x2924) has exited with code 0 (0x0).
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Users\i51864\Documents\Visual Studio 2012\Projects\CassandraBlobInsertTest\CassandraBlobInsertTest\bin\Debug\CassandraBlobInsertTest.exe', Symbols loaded.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Users\i51864\Documents\Visual Studio 2012\Projects\CassandraBlobInsertTest\CassandraBlobInsertTest\bin\Debug\CassandraSharp.dll', Symbols loaded.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'CassandraBlobInsertTest.vshost.exe' (Managed (v4.0.30319)): Loaded 'Microsoft.GeneratedCode'
The thread 'vshost.RunParkingWindow' (0xe5c) has exited with code 0 (0x0).
The thread '<No Name>' (0x3e08) has exited with code 0 (0x0).
The program '[14084] CassandraBlobInsertTest.vshost.exe: Program Trace' has exited with code 0 (0x0).
The program '[14084] CassandraBlobInsertTest.vshost.exe: Managed (v4.0.30319)' has exited with code 0 (0x0).

and this is how Cassandra bombs, killing all clients including cqlsh connected to it. The only way to do anything after is to restart the clients (and sometimes Cassandra itself).

 INFO 10:16:43,149 Completed flushing \var\lib\cassandra\data\system\schema_colu
mnfamilies\system-schema_columnfamilies-ia-78-Data.db (649 bytes) for commitlog
position ReplayPosition(segmentId=1357915241333, position=538033)
 INFO 10:16:43,150 Enqueuing flush of Memtable-schema_columns@14121625(229/229 s
erialized/live bytes, 5 ops)
 INFO 10:16:43,152 Writing Memtable-schema_columns@14121625(229/229 serialized/l
ive bytes, 5 ops)
 INFO 10:16:43,297 Completed flushing \var\lib\cassandra\data\system\schema_colu
mns\system-schema_columns-ia-46-Data.db (195 bytes) for commitlog position Repla
yPosition(segmentId=1357915241333, position=538033)
 WARN 10:16:43,543 setting live ratio to minimum of 1.0 instead of 0.04133466533
466534
 INFO 10:16:43,543 CFS(Keyspace='foo', ColumnFamily='bar') liveRatio is 1.0 (jus
t-counted was 1.0).  calculation took 9ms for 134 columns
ERROR 10:16:44,597 Unexpected exception during request
java.io.IOException: An existing connection was forcibly closed by the remote ho
st
        at sun.nio.ch.SocketDispatcher.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(Unknown Source)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
        at sun.nio.ch.IOUtil.read(Unknown Source)
        at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:59)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedK
eys(AbstractNioWorker.java:472)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioW
orker.java:333)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source
)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
@hjarraya

getting same error now

 WARN [MemoryMeter:1] 2013-01-11 15:42:15,628 Memtable.java (line 191) setting live ratio to minimum of 1.0 instead of 0.21294801762114537
 INFO [MemoryMeter:1] 2013-01-11 15:42:15,631 Memtable.java (line 207) CFS(Keyspace='foo', ColumnFamily='bar') liveRatio is 1.0 (just-counted was 1.0).  calculation took 16ms for 200 columns
ERROR [Native-Transport-Requests:59] 2013-01-11 15:42:42,047 ErrorMessage.java (line 197) Unexpected exception during request
java.io.IOException: An existing connection was forcibly closed by the remote host
    at sun.nio.ch.SocketDispatcher.read0(Native Method)
    at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
    at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
    at sun.nio.ch.IOUtil.read(IOUtil.java:166)
    at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:245)
    at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:59)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:472)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:333)
    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
@pchalamet
Owner

I've run your code successfully running /master/LATEST. Using cqlplus, I managed to query the cf:

localhost> use Foo;
localhost> select * from foo.bar where id=99;
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| F2A8DE796AB01311ADF916B69F8E33CD8BD233C~ | 99      |
+------------------------------------------+---------+

Could you tell me more about your configuration ?

@ananthonline

I am running a single machine cluster on localhost with no changes from default other than to enable native transport. Also - I'd recommend inserting more than one record, perhaps 10 or so. Were you able to run my test code from above without any errors?

Are there any settings that need to be changed in cassandra.yaml? Does native transport use the same values as thrift_framed_transport_size_in_mb and thrift_max_message_length_in_mb? Could this even be the result of some sort of "message size" exceeded condition?

Although this is not exactly the same, this (http://mail-archives.apache.org/mod_mbox/thrift-user/201105.mbox/%3CBANLkTimv11naZkJ6iUFz8VojH_HUyv_Eug@mail.gmail.com%3E) looks very much like the error I'm encountering.

@ananthonline

Bump

I'm still getting this error and can't use cassandra-sharp until I resolve this problem. Any help would be most appreciated. It looks like @hjarraya also sees the same exception.

@pchalamet
Owner
@ananthonline

I am running Cassandra 1.2.0-rc2 on Windows 7 x64 under .NET 4.5 (specified in the app.config file, startup section). I have 4 cores on my system (Q9400 @ 2.44 GHz quad core with 4 GB of RAM).

My cassandra config follows

# Cassandra storage config YAML 

# NOTE:
#   See http://wiki.apache.org/cassandra/StorageConfiguration for
#   full explanations of configuration directives
# /NOTE

# The name of the cluster. This is mainly used to prevent machines in
# one logical cluster from joining another.
cluster_name: 'Test Cluster'

# This defines the number of tokens randomly assigned to this node on the ring
# The more tokens, relative to other nodes, the larger the proportion of data
# that this node will store. You probably want all nodes to have the same number
# of tokens assuming they have equal hardware capability.
#
# If you leave this unspecified, Cassandra will use the default of 1 token for legacy compatibility,
# and will use the initial_token as described below.
#
# Specifying initial_token will override this setting.
#
# If you already have a cluster with 1 token per node, and wish to migrate to 
# multiple tokens per node, see http://wiki.apache.org/cassandra/Operations
# num_tokens: 256

# If you haven't specified num_tokens, or have set it to the default of 1 then
# you should always specify InitialToken when setting up a production
# cluster for the first time, and often when adding capacity later.
# The principle is that each node should be given an equal slice of
# the token ring; see http://wiki.apache.org/cassandra/Operations
# for more details.
#
# If blank, Cassandra will request a token bisecting the range of
# the heaviest-loaded existing node.  If there is no load information
# available, such as is the case with a new cluster, it will pick
# a random token, which will lead to hot spots.
initial_token:

# See http://wiki.apache.org/cassandra/HintedHandoff
hinted_handoff_enabled: true
# this defines the maximum amount of time a dead host will have hints
# generated.  After it has been dead this long, hints will be dropped.
max_hint_window_in_ms: 10800000 # 3 hours
# throttle in KB's per second, per delivery thread
hinted_handoff_throttle_in_kb: 1024
# Number of threads with which to deliver hints;
# Consider increasing this number when you have multi-dc deployments, since
# cross-dc handoff tends to be slower
max_hints_delivery_threads: 2

# The following setting populates the page cache on memtable flush and compaction
# WARNING: Enable this setting only when the whole node's data fits in memory.
# Defaults to: false
# populate_io_cache_on_flush: false

# authentication backend, implementing IAuthenticator; used to identify users
authenticator: org.apache.cassandra.auth.AllowAllAuthenticator

# authorization backend, implementing IAuthorizer; used to limit access/provide permissions
authorizer: org.apache.cassandra.auth.AllowAllAuthorizer

# The partitioner is responsible for distributing rows (by key) across
# nodes in the cluster.  Any IPartitioner may be used, including your
# own as long as it is on the classpath.  Out of the box, Cassandra
# provides org.apache.cassandra.dht.{Murmur3Partitioner, RandomPartitioner
# ByteOrderedPartitioner, OrderPreservingPartitioner (deprecated)}.
# 
# - RandomPartitioner distributes rows across the cluster evenly by md5.
#   This is the default prior to 1.2 and is retained for compatibility.
# - Murmur3Partitioner is similar to RandomPartioner but uses Murmur3_128
#   Hash Function instead of md5.  When in doubt, this is the best option.
# - ByteOrderedPartitioner orders rows lexically by key bytes.  BOP allows
#   scanning rows in key order, but the ordering can generate hot spots
#   for sequential insertion workloads.
# - OrderPreservingPartitioner is an obsolete form of BOP, that stores
# - keys in a less-efficient format and only works with keys that are
#   UTF8-encoded Strings.
# - CollatingOPP colates according to EN,US rules rather than lexical byte
#   ordering.  Use this as an example if you need custom collation.
#
# See http://wiki.apache.org/cassandra/Operations for more on
# partitioners and token selection.
partitioner: org.apache.cassandra.dht.Murmur3Partitioner

# directories where Cassandra should store data on disk.
data_file_directories:
    - /var/lib/cassandra/data

# commit log
commitlog_directory: /var/lib/cassandra/commitlog

# policy for data disk failures:
# stop: shut down gossip and Thrift, leaving the node effectively dead, but
#       still inspectable via JMX.
# best_effort: stop using the failed disk and respond to requests based on
#              remaining available sstables.  This means you WILL see obsolete
#              data at CL.ONE!
# ignore: ignore fatal errors and let requests fail, as in pre-1.2 Cassandra
disk_failure_policy: stop

# Maximum size of the key cache in memory.
#
# Each key cache hit saves 1 seek and each row cache hit saves 2 seeks at the
# minimum, sometimes more. The key cache is fairly tiny for the amount of
# time it saves, so it's worthwhile to use it at large numbers.
# The row cache saves even more time, but must store the whole values of
# its rows, so it is extremely space-intensive. It's best to only use the
# row cache if you have hot rows or static rows.
#
# NOTE: if you reduce the size, you may not get you hottest keys loaded on startup.
#
# Default value is empty to make it "auto" (min(5% of Heap (in MB), 100MB)). Set to 0 to disable key cache.
key_cache_size_in_mb:

# Duration in seconds after which Cassandra should
# safe the keys cache. Caches are saved to saved_caches_directory as
# specified in this configuration file.
#
# Saved caches greatly improve cold-start speeds, and is relatively cheap in
# terms of I/O for the key cache. Row cache saving is much more expensive and
# has limited use.
#
# Default is 14400 or 4 hours.
key_cache_save_period: 14400

# Number of keys from the key cache to save
# Disabled by default, meaning all keys are going to be saved
# key_cache_keys_to_save: 100

# Maximum size of the row cache in memory.
# NOTE: if you reduce the size, you may not get you hottest keys loaded on startup.
#
# Default value is 0, to disable row caching.
row_cache_size_in_mb: 0

# Duration in seconds after which Cassandra should
# safe the row cache. Caches are saved to saved_caches_directory as specified
# in this configuration file.
#
# Saved caches greatly improve cold-start speeds, and is relatively cheap in
# terms of I/O for the key cache. Row cache saving is much more expensive and
# has limited use.
#
# Default is 0 to disable saving the row cache.
row_cache_save_period: 0

# Number of keys from the row cache to save
# Disabled by default, meaning all keys are going to be saved
# row_cache_keys_to_save: 100

# The provider for the row cache to use.
#
# Supported values are: ConcurrentLinkedHashCacheProvider, SerializingCacheProvider
#
# SerializingCacheProvider serialises the contents of the row and stores
# it in native memory, i.e., off the JVM Heap. Serialized rows take
# significantly less memory than "live" rows in the JVM, so you can cache
# more rows in a given memory footprint.  And storing the cache off-heap
# means you can use smaller heap sizes, reducing the impact of GC pauses.
#
# It is also valid to specify the fully-qualified class name to a class
# that implements org.apache.cassandra.cache.IRowCacheProvider.
#
# Defaults to SerializingCacheProvider
row_cache_provider: SerializingCacheProvider

# saved caches
saved_caches_directory: /var/lib/cassandra/saved_caches

# commitlog_sync may be either "periodic" or "batch." 
# When in batch mode, Cassandra won't ack writes until the commit log
# has been fsynced to disk.  It will wait up to
# commitlog_sync_batch_window_in_ms milliseconds for other writes, before
# performing the sync.
#
# commitlog_sync: batch
# commitlog_sync_batch_window_in_ms: 50
#
# the other option is "periodic" where writes may be acked immediately
# and the CommitLog is simply synced every commitlog_sync_period_in_ms
# milliseconds.
commitlog_sync: periodic
commitlog_sync_period_in_ms: 10000

# The size of the individual commitlog file segments.  A commitlog
# segment may be archived, deleted, or recycled once all the data
# in it (potentally from each columnfamily in the system) has been 
# flushed to sstables.  
#
# The default size is 32, which is almost always fine, but if you are
# archiving commitlog segments (see commitlog_archiving.properties),
# then you probably want a finer granularity of archiving; 8 or 16 MB
# is reasonable.
commitlog_segment_size_in_mb: 32

# any class that implements the SeedProvider interface and has a
# constructor that takes a Map<String, String> of parameters will do.
seed_provider:
    # Addresses of hosts that are deemed contact points. 
    # Cassandra nodes use this list of hosts to find each other and learn
    # the topology of the ring.  You must change this if you are running
    # multiple nodes!
    - class_name: org.apache.cassandra.locator.SimpleSeedProvider
      parameters:
          # seeds is actually a comma-delimited list of addresses.
          # Ex: "<ip1>,<ip2>,<ip3>"
          - seeds: "127.0.0.1"

# emergency pressure valve: each time heap usage after a full (CMS)
# garbage collection is above this fraction of the max, Cassandra will
# flush the largest memtables.  
#
# Set to 1.0 to disable.  Setting this lower than
# CMSInitiatingOccupancyFraction is not likely to be useful.
#
# RELYING ON THIS AS YOUR PRIMARY TUNING MECHANISM WILL WORK POORLY:
# it is most effective under light to moderate load, or read-heavy
# workloads; under truly massive write load, it will often be too
# little, too late.
flush_largest_memtables_at: 0.75

# emergency pressure valve #2: the first time heap usage after a full
# (CMS) garbage collection is above this fraction of the max,
# Cassandra will reduce cache maximum _capacity_ to the given fraction
# of the current _size_.  Should usually be set substantially above
# flush_largest_memtables_at, since that will have less long-term
# impact on the system.  
# 
# Set to 1.0 to disable.  Setting this lower than
# CMSInitiatingOccupancyFraction is not likely to be useful.
reduce_cache_sizes_at: 0.85
reduce_cache_capacity_to: 0.6

# For workloads with more data than can fit in memory, Cassandra's
# bottleneck will be reads that need to fetch data from
# disk. "concurrent_reads" should be set to (16 * number_of_drives) in
# order to allow the operations to enqueue low enough in the stack
# that the OS and drives can reorder them.
#
# On the other hand, since writes are almost never IO bound, the ideal
# number of "concurrent_writes" is dependent on the number of cores in
# your system; (8 * number_of_cores) is a good rule of thumb.
concurrent_reads: 32
concurrent_writes: 32

# Total memory to use for memtables.  Cassandra will flush the largest
# memtable when this much memory is used.
# If omitted, Cassandra will set it to 1/3 of the heap.
# memtable_total_space_in_mb: 2048

# Total space to use for commitlogs.  Since commitlog segments are
# mmapped, and hence use up address space, the default size is 32
# on 32-bit JVMs, and 1024 on 64-bit JVMs.
#
# If space gets above this value (it will round up to the next nearest
# segment multiple), Cassandra will flush every dirty CF in the oldest
# segment and remove it.  So a small total commitlog space will tend
# to cause more flush activity on less-active columnfamilies.
# commitlog_total_space_in_mb: 4096

# This sets the amount of memtable flush writer threads.  These will
# be blocked by disk io, and each one will hold a memtable in memory
# while blocked. If you have a large heap and many data directories,
# you can increase this value for better flush performance.
# By default this will be set to the amount of data directories defined.
#memtable_flush_writers: 1

# the number of full memtables to allow pending flush, that is,
# waiting for a writer thread.  At a minimum, this should be set to
# the maximum number of secondary indexes created on a single CF.
memtable_flush_queue_size: 4

# Whether to, when doing sequential writing, fsync() at intervals in
# order to force the operating system to flush the dirty
# buffers. Enable this to avoid sudden dirty buffer flushing from
# impacting read latencies. Almost always a good idea on SSD:s; not
# necessarily on platters.
trickle_fsync: false
trickle_fsync_interval_in_kb: 10240

# TCP port, for commands and data
storage_port: 7000

# SSL port, for encrypted communication.  Unused unless enabled in
# encryption_options
ssl_storage_port: 7001

# Address to bind to and tell other Cassandra nodes to connect to. You
# _must_ change this if you want multiple nodes to be able to
# communicate!
# 
# Leaving it blank leaves it up to InetAddress.getLocalHost(). This
# will always do the Right Thing *if* the node is properly configured
# (hostname, name resolution, etc), and the Right Thing is to use the
# address associated with the hostname (it might not be).
#
# Setting this to 0.0.0.0 is always wrong.
listen_address: localhost

# Address to broadcast to other Cassandra nodes
# Leaving this blank will set it to the same value as listen_address
# broadcast_address: 1.2.3.4


# Whether to start the native transport server.
# Currently, only the thrift server is started by default because the native
# transport is considered beta.
# Please note that the address on which the native transport is bound is the
# same as the rpc_address. The port however is different and specified below.
start_native_transport: true
# port for the CQL native transport to listen for clients on
native_transport_port: 9042
# The minimum and maximum threads for handling requests when the native
# transport is used. The meaning is those is similar to the one of
# rpc_min_threads and rpc_max_threads, though the default differ slightly and
# are the ones below:
# native_transport_min_threads: 16
# native_transport_max_threads: 128


# Whether to start the thrift rpc server.
start_rpc: true
# The address to bind the Thrift RPC service to -- clients connect
# here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if
# you want Thrift to listen on all interfaces.
# 
# Leaving this blank has the same effect it does for ListenAddress,
# (i.e. it will be based on the configured hostname of the node).
rpc_address: localhost
# port for Thrift to listen for clients on
rpc_port: 9160

# enable or disable keepalive on rpc connections
rpc_keepalive: true

# Cassandra provides three out-of-the-box options for the RPC Server:
#
# sync  -> One thread per thrift connection. For a very large number of clients, memory
#          will be your limiting factor. On a 64 bit JVM, 128KB is the minimum stack size
#          per thread, and that will correspond to your use of virtual memory (but physical memory
#          may be limited depending on use of stack space).
#
# hsha  -> Stands for "half synchronous, half asynchronous." All thrift clients are handled
#          asynchronously using a small number of threads that does not vary with the amount
#          of thrift clients (and thus scales well to many clients). The rpc requests are still
#          synchronous (one thread per active request).
#
# The default is sync because on Windows hsha is about 30% slower.  On Linux,
# sync/hsha performance is about the same, with hsha of course using less memory.
#
# Alternatively,  can provide your own RPC server by providing the fully-qualified class name
# of an o.a.c.t.TServerFactory that can create an instance of it.
rpc_server_type: sync

# Uncomment rpc_min|max_thread to set request pool size limits.
#
# Regardless of your choice of RPC server (see above), the number of maximum requests in the
# RPC thread pool dictates how many concurrent requests are possible (but if you are using the sync
# RPC server, it also dictates the number of clients that can be connected at all).
#
# The default is unlimited and thus provide no protection against clients overwhelming the server. You are
# encouraged to set a maximum that makes sense for you in production, but do keep in mind that
# rpc_max_threads represents the maximum number of client requests this server may execute concurrently.
#
# rpc_min_threads: 16
# rpc_max_threads: 2048

# uncomment to set socket buffer sizes on rpc connections
# rpc_send_buff_size_in_bytes:
# rpc_recv_buff_size_in_bytes:

# Frame size for thrift (maximum field length).
thrift_framed_transport_size_in_mb: 15

# The max length of a thrift message, including all fields and
# internal thrift overhead.
thrift_max_message_length_in_mb: 16

# Set to true to have Cassandra create a hard link to each sstable
# flushed or streamed locally in a backups/ subdirectory of the
# Keyspace data.  Removing these links is the operator's
# responsibility.
incremental_backups: false

# Whether or not to take a snapshot before each compaction.  Be
# careful using this option, since Cassandra won't clean up the
# snapshots for you.  Mostly useful if you're paranoid when there
# is a data format change.
snapshot_before_compaction: false

# Whether or not a snapshot is taken of the data before keyspace truncation
# or dropping of column families. The STRONGLY advised default of true 
# should be used to provide data safety. If you set this flag to false, you will
# lose data on truncation or drop.
auto_snapshot: true

# Add column indexes to a row after its contents reach this size.
# Increase if your column values are large, or if you have a very large
# number of columns.  The competing causes are, Cassandra has to
# deserialize this much of the row to read a single column, so you want
# it to be small - at least if you do many partial-row reads - but all
# the index data is read for each access, so you don't want to generate
# that wastefully either.
column_index_size_in_kb: 64

# Size limit for rows being compacted in memory.  Larger rows will spill
# over to disk and use a slower two-pass compaction process.  A message
# will be logged specifying the row key.
in_memory_compaction_limit_in_mb: 64

# Number of simultaneous compactions to allow, NOT including
# validation "compactions" for anti-entropy repair.  Simultaneous
# compactions can help preserve read performance in a mixed read/write
# workload, by mitigating the tendency of small sstables to accumulate
# during a single long running compactions. The default is usually
# fine and if you experience problems with compaction running too
# slowly or too fast, you should look at
# compaction_throughput_mb_per_sec first.
#
# concurrent_compactors defaults to the number of cores.
# Uncomment to make compaction mono-threaded, the pre-0.8 default.
#concurrent_compactors: 1

# Multi-threaded compaction. When enabled, each compaction will use
# up to one thread per core, plus one thread per sstable being merged.
# This is usually only useful for SSD-based hardware: otherwise, 
# your concern is usually to get compaction to do LESS i/o (see:
# compaction_throughput_mb_per_sec), not more.
multithreaded_compaction: false

# Throttles compaction to the given total throughput across the entire
# system. The faster you insert data, the faster you need to compact in
# order to keep the sstable count down, but in general, setting this to
# 16 to 32 times the rate you are inserting data is more than sufficient.
# Setting this to 0 disables throttling. Note that this account for all types
# of compaction, including validation compaction.
compaction_throughput_mb_per_sec: 16

# Track cached row keys during compaction, and re-cache their new
# positions in the compacted sstable.  Disable if you use really large
# key caches.
compaction_preheat_key_cache: true

# Throttles all outbound streaming file transfers on this node to the
# given total throughput in Mbps. This is necessary because Cassandra does
# mostly sequential IO when streaming data during bootstrap or repair, which
# can lead to saturating the network connection and degrading rpc performance.
# When unset, the default is 400 Mbps or 50 MB/s.
# stream_throughput_outbound_megabits_per_sec: 400

# How long the coordinator should wait for read operations to complete
read_request_timeout_in_ms: 10000
# How long the coordinator should wait for seq or index scans to complete
range_request_timeout_in_ms: 10000
# How long the coordinator should wait for writes to complete
write_request_timeout_in_ms: 10000
# How long the coordinator should wait for truncates to complete
# (This can be much longer, because unless auto_snapshot is disabled
# we need to flush first so we can snapshot before removing the data.)
truncate_request_timeout_in_ms: 60000
# The default timeout for other, miscellaneous operations
request_timeout_in_ms: 10000

# Enable operation timeout information exchange between nodes to accurately
# measure request timeouts, If disabled cassandra will assuming the request
# was forwarded to the replica instantly by the coordinator
#
# Warning: before enabling this property make sure to ntp is installed
# and the times are synchronized between the nodes.
cross_node_timeout: false

# Enable socket timeout for streaming operation.
# When a timeout occurs during streaming, streaming is retried from the start
# of the current file. This *can* involve re-streaming an important amount of
# data, so you should avoid setting the value too low.
# Default value is 0, which never timeout streams.
# streaming_socket_timeout_in_ms: 0

# phi value that must be reached for a host to be marked down.
# most users should never need to adjust this.
# phi_convict_threshold: 8

# endpoint_snitch -- Set this to a class that implements
# IEndpointSnitch.  The snitch has two functions:
# - it teaches Cassandra enough about your network topology to route
#   requests efficiently
# - it allows Cassandra to spread replicas around your cluster to avoid
#   correlated failures. It does this by grouping machines into
#   "datacenters" and "racks."  Cassandra will do its best not to have
#   more than one replica on the same "rack" (which may not actually
#   be a physical location)
#
# IF YOU CHANGE THE SNITCH AFTER DATA IS INSERTED INTO THE CLUSTER,
# YOU MUST RUN A FULL REPAIR, SINCE THE SNITCH AFFECTS WHERE REPLICAS
# ARE PLACED.
#
# Out of the box, Cassandra provides
#  - SimpleSnitch:
#    Treats Strategy order as proximity. This improves cache locality
#    when disabling read repair, which can further improve throughput.
#    Only appropriate for single-datacenter deployments.
#  - PropertyFileSnitch:
#    Proximity is determined by rack and data center, which are
#    explicitly configured in cassandra-topology.properties.
#  - GossipingPropertyFileSnitch
#    The rack and datacenter for the local node are defined in
#    cassandra-rackdc.properties and propagated to other nodes via gossip.  If
#    cassandra-topology.properties exists, it is used as a fallback, allowing
#    migration from the PropertyFileSnitch.
#  - RackInferringSnitch:
#    Proximity is determined by rack and data center, which are
#    assumed to correspond to the 3rd and 2nd octet of each node's
#    IP address, respectively.  Unless this happens to match your
#    deployment conventions (as it did Facebook's), this is best used
#    as an example of writing a custom Snitch class.
#  - Ec2Snitch:
#    Appropriate for EC2 deployments in a single Region.  Loads Region
#    and Availability Zone information from the EC2 API. The Region is
#    treated as the Datacenter, and the Availability Zone as the rack.
#    Only private IPs are used, so this will not work across multiple
#    Regions.
#  - Ec2MultiRegionSnitch:
#    Uses public IPs as broadcast_address to allow cross-region
#    connectivity.  (Thus, you should set seed addresses to the public
#    IP as well.) You will need to open the storage_port or
#    ssl_storage_port on the public IP firewall.  (For intra-Region
#    traffic, Cassandra will switch to the private IP after
#    establishing a connection.)
#
# You can use a custom Snitch by setting this to the full class name
# of the snitch, which will be assumed to be on your classpath.
endpoint_snitch: SimpleSnitch

# controls how often to perform the more expensive part of host score
# calculation
dynamic_snitch_update_interval_in_ms: 100 
# controls how often to reset all host scores, allowing a bad host to
# possibly recover
dynamic_snitch_reset_interval_in_ms: 600000
# if set greater than zero and read_repair_chance is < 1.0, this will allow
# 'pinning' of replicas to hosts in order to increase cache capacity.
# The badness threshold will control how much worse the pinned host has to be
# before the dynamic snitch will prefer other replicas over it.  This is
# expressed as a double which represents a percentage.  Thus, a value of
# 0.2 means Cassandra would continue to prefer the static snitch values
# until the pinned host was 20% worse than the fastest.
dynamic_snitch_badness_threshold: 0.1

# request_scheduler -- Set this to a class that implements
# RequestScheduler, which will schedule incoming client requests
# according to the specific policy. This is useful for multi-tenancy
# with a single Cassandra cluster.
# NOTE: This is specifically for requests from the client and does
# not affect inter node communication.
# org.apache.cassandra.scheduler.NoScheduler - No scheduling takes place
# org.apache.cassandra.scheduler.RoundRobinScheduler - Round robin of
# client requests to a node with a separate queue for each
# request_scheduler_id. The scheduler is further customized by
# request_scheduler_options as described below.
request_scheduler: org.apache.cassandra.scheduler.NoScheduler

# Scheduler Options vary based on the type of scheduler
# NoScheduler - Has no options
# RoundRobin
#  - throttle_limit -- The throttle_limit is the number of in-flight
#                      requests per client.  Requests beyond 
#                      that limit are queued up until
#                      running requests can complete.
#                      The value of 80 here is twice the number of
#                      concurrent_reads + concurrent_writes.
#  - default_weight -- default_weight is optional and allows for
#                      overriding the default which is 1.
#  - weights -- Weights are optional and will default to 1 or the
#               overridden default_weight. The weight translates into how
#               many requests are handled during each turn of the
#               RoundRobin, based on the scheduler id.
#
# request_scheduler_options:
#    throttle_limit: 80
#    default_weight: 5
#    weights:
#      Keyspace1: 1
#      Keyspace2: 5

# request_scheduler_id -- An identifer based on which to perform
# the request scheduling. Currently the only valid option is keyspace.
# request_scheduler_id: keyspace

# index_interval controls the sampling of entries from the primrary
# row index in terms of space versus time.  The larger the interval,
# the smaller and less effective the sampling will be.  In technicial
# terms, the interval coresponds to the number of index entries that
# are skipped between taking each sample.  All the sampled entries
# must fit in memory.  Generally, a value between 128 and 512 here
# coupled with a large key cache size on CFs results in the best trade
# offs.  This value is not often changed, however if you have many
# very small rows (many to an OS page), then increasing this will
# often lower memory usage without a impact on performance.
index_interval: 128

# Enable or disable inter-node encryption
# Default settings are TLS v1, RSA 1024-bit keys (it is imperative that
# users generate their own keys) TLS_RSA_WITH_AES_128_CBC_SHA as the cipher
# suite for authentication, key exchange and encryption of the actual data transfers.
# NOTE: No custom encryption options are enabled at the moment
# The available internode options are : all, none, dc, rack
#
# If set to dc cassandra will encrypt the traffic between the DCs
# If set to rack cassandra will encrypt the traffic between the racks
#
# The passwords used in these options must match the passwords used when generating
# the keystore and truststore.  For instructions on generating these files, see:
# http://download.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore
#
server_encryption_options:
    internode_encryption: none
    keystore: conf/.keystore
    keystore_password: cassandra
    truststore: conf/.truststore
    truststore_password: cassandra
    # More advanced defaults below:
    # protocol: TLS
    # algorithm: SunX509
    # store_type: JKS
    # cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA]

# enable or disable client/server encryption.
client_encryption_options:
    enabled: false
    keystore: conf/.keystore
    keystore_password: cassandra
    # More advanced defaults below:
    # protocol: TLS
    # algorithm: SunX509
    # store_type: JKS
    # cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA]

# internode_compression controls whether traffic between nodes is
# compressed.
# can be:  all  - all traffic is compressed
#          dc   - traffic between different datacenters is compressed
#          none - nothing is compressed.
internode_compression: all

Where would I find my JVM configuration? I am running the latest JRE version 7, update 11.

Thanks!

@pchalamet
Owner

Everything runs fine under .NET 4.5 x64 but I'm running a Java 1.6 x86 (1.6.0_37).
Would you mind trying with an x86 1.6 jvm please ?
I will try with a x64 1.7 JVM on my side.

@pchalamet
Owner
@ananthonline

Thanks for running it through the x64 JVM, Pierre. I checked with 1.6 x86 and the latest sources from master, but the error still exists. I am beginning to think it has something to do with message sizes. Perhaps your setting of

# Frame size for thrift (maximum field length).
thrift_framed_transport_size_in_mb: 15

# The max length of a thrift message, including all fields and
# internal thrift overhead.
thrift_max_message_length_in_mb: 16

are different from mine?

Also, samples/preparedstatement/batch.cs runs fine because the columns are primitive data types - batch insert using prepared queries where all columns are primitive data types work just fine. The problem happens when I make one of the columns a blob and write more than 5000 bytes to it (I tried with 25000 because I need that amount of data in a column for an application).

@hjarraya
@pchalamet
Owner
@ananthonline

Scratch my last. The sample runs but Cassandra still throws the exception and I can't read back whats been inserted without crashing everything.

localhost> use Foo;
localhost> select * from Bar where id=2;
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| 5D9A99C1E3018B2CDA0AE1B7E57FF57CE16F615~ | 2       |
+------------------------------------------+---------+
localhost> select * from Bar where id=9999;
+------------------------------------------+-----------+
| baz                                      | id        |
+==========================================+===========+
| EE9E771C95FE123B72B55D60891A941BEC19A11~ | 9999      |
+------------------------------------------+-----------+
localhost> select * from Bar where id=1;
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| 2652E0995799B64A7A6AC46A8956EA95FD21075~ | 1       |
+------------------------------------------+---------+
localhost> select * from Bar where id=10;
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| D225A7E757B9EF404D732EC946C2AD947EB7759~ | 10      |
+------------------------------------------+---------+
localhost> select * from Bar where id in (1, 2, 3, 5);
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| 2652E0995799B64A7A6AC46A8956EA95FD21075~ | 1       |
+------------------------------------------+---------+
| 5D9A99C1E3018B2CDA0AE1B7E57FF57CE16F615~ | 2       |
+------------------------------------------+---------+
Command execution failed with error 'Unexpected read count'
localhost> select * from Bar where id=10;
Command execution failed with error 'Can't find any valid endpoint'
localhost>

After this point - cqlplus does not work unless I quit and restart it.

@pchalamet
Owner

could you run "!set log=true" before select'ing ?
This will display debug info and the callstack.

Thanks.

@pchalamet
Owner

Could you upgrade to Cassandra 1.2 (nothing has really changed between rc2 and rtm but just in case).
It's strange to receive "ClientRequestAbortedException". I thought it was not used anymore and I just forgot to remove it... Are you sure you are running latest sources from master ?

Btw, thrift message size has no impact on cql binary transport.

@ananthonline

I am running the latest sources from master, I see you've updated your Batch.cs with blobs and even the field names from my code. I am now using this code to perform my tests (not my sample). Like I said - the code runs, but I always see this exception in the Cassandra window around the time the batch insert is finishing

ERROR 16:33:20,899 Unexpected exception during request
java.io.IOException: An existing connection was forcibly closed by the remote host
        at sun.nio.ch.SocketDispatcher.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(Unknown Source)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
        at sun.nio.ch.IOUtil.read(Unknown Source)
        at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:59)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:472)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:333)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

Then - the first few queries I run in cqlplus works just fine - then I get the

Command execution failed with error 'Unexpected read count'

and then cqlplus will always show me

Command execution failed with error 'Can't find any valid endpoint'

till I restart it - and then I'll get the Unexpected read count error again.

Here's a sample session.

Connecting to localhost:9042...
+------------------+-----------------+-----------+----------------------+
| cluster_name     | data_center     | rack      | release_version      |
+==================+=================+===========+======================+
| Test Cluster     | datacenter1     | rack1     | 1.2.0                |
+------------------+-----------------+-----------+----------------------+
Commands:
  !help   - display help
  !set    - set environment variable
              -> MaxWidth=[int] : set max result column width
              -> Output=[Tab,KV,CSV] : select output formatter
              -> Log=[bool] : enable debug log to console
  !exit   - exit cqlplus
  !reset  - reset environment
  !cls    - clear screen
  !exec   - execute statement
              -> Statement=<string> : Statement string
  !source - load statements from specific file
              -> File=<string> : File containing statements
  CQL query

Examples:
  !set log=true colwidth=20;
  select * from system.local;
localhost> use Foo;
localhost> select * from Bar where id in (1, 2, 3, 4, 5, 9999);
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| DF818F6BBB00B061E20511CE56AD9B1251DD4D1~ | 1       |
+------------------------------------------+---------+
Command execution failed with error 'Unexpected read count'
localhost> select * from Bar where id in (1, 2, 3, 4, 5, 9999);
Command execution failed with error 'no keyspace has been specified'
localhost> select * from Foo.Bar where id in (1, 2, 3, 4, 5, 9999);
+------------------------------------------+---------+
| baz                                      | id      |
+==========================================+=========+
| DF818F6BBB00B061E20511CE56AD9B1251DD4D1~ | 1       |
+------------------------------------------+---------+
Command execution failed with error 'Unexpected read count'
localhost> select * from Foo.Bar where id in (1, 2, 3, 4, 5, 9999);
Command execution failed with error 'Can't find any valid endpoint'
localhost>

This is after running your Batch.cs, BTW. Also note that I didn't change ANYTHING in cassandra.yaml except for start_native_transport.

I appreciate your effort in trying to help me fix this problem, thanks!

@pchalamet
Owner

Being enable to query the cluster after a transport error is "normal". The endpoint is banned and you have a single endpoint.

If you wait a little bit, the endpoint will be recovered and you will be able to query again. You can enable debug log with "!set log=true" to see recovery log (wait 1 minute).

I've been able to get one repro (same error actually) but only one time and failed to backup storage unfortunately. But I'm sure you are hitting a Cassandra bug there (unexception exception server side). Could you enable DEBUG in Cassandra (conf/log4j-server.properties) and see what's happening ?

Probably this worth raising an issue on the cassandra user list if you have a good repro and a meaningful exception in Cassandra log.

@ananthonline

Ok - so the DEBUG log reads like so

DEBUG 16:59:56,552 Received: PREPARE INSERT INTO Foo.Bar (id, Baz) VALUES (?, ?
DEBUG 16:59:56,554 request complete
DEBUG 16:59:56,555 Responding: RESULT PREPARED f7080daad4b908a71d1d416359be3469[id(foo, bar), org.apache.cassandra.db.marshal.Int32Type][baz(foo, bar), org.apche.cassandra.db.marshal.BytesType]
DEBUG 16:59:56,598 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 vaues at consistency ONE
DEBUG 16:59:56,600 request complete
DEBUG 16:59:56,600 Responding: EMPTY RESULT
DEBUG 16:59:56,605 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 vaues at consistency ONE
DEBUG 16:59:56,607 request complete
DEBUG 16:59:56,607 Responding: EMPTY RESULT
DEBUG 16:59:56,616 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 vaues at consistency ONE
DEBUG 16:59:56,618 request complete
DEBUG 16:59:56,618 Responding: EMPTY RESULT
DEBUG 16:59:56,625 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 vaues at consistency ONE
DEBUG 16:59:56,627 request complete
DEBUG 16:59:56,628 Responding: EMPTY RESULT
DEBUG 16:59:56,633 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 vaues at consistency ONE
DEBUG 16:59:56,637 request complete
DEBUG 16:59:56,638 Responding: EMPTY RESULT
ERROR 16:59:56,652 Unexpected exception during request
java.io.IOException: An existing connection was forcibly closed by the remote hst
        at sun.nio.ch.SocketDispatcher.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(Unknown Source)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
        at sun.nio.ch.IOUtil.read(Unknown Source)
        at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:59)        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedeys(AbstractNioWorker.java:472)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioorker.java:333)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
DEBUG 16:59:56,669 Renaming \var\lib\cassandra\data\system\schema_columnfamilie\system-schema_columnfamilies-tmp-ia-146-Index.db to \var\lib\cassandra\data\sytem\schema_columnfamilies\system-schema_columnfamilies-ia-146-Index.db
DEBUG 16:59:56,676 Renaming \var\lib\cassandra\data\system\schema_columnfamilie\system-schema_columnfamilies-tmp-ia-146-TOC.txt to \var\lib\cassandra\data\sysem\schema_columnfamilies\system-schema_columnfamilies-ia-146-TOC.txt
DEBUG 16:59:56,679 Renaming \var\lib\cassandra\data\system\schema_columnfamilie\system-schema_columnfamilies-tmp-ia-146-CompressionInfo.db to 

I modified count to 5 - so I'm only running insert 5 times and each time I insert the key and 25000 bytes. I get this error consistently.

@pchalamet
Owner

Before raising the issue to cassandra user list, you probably want to increase thread stack under java 7
(see https://issues.apache.org/jira/browse/CASSANDRA-4275).

==> can you then display the full stack of the cassandra-sharp exception ? (!set log=true in cqlplus).

@pchalamet
Owner

OK found the bug - Stream.Read does not always return the requested number of bytes (fixed in WindowedReadStream). Had to use another server with more core to exhibit the problem.

Fix pushed to master. Could you give it a try ? Thanks.

@ananthonline

Yep - that fixed it. Thank you for fixing this issue for me. I am using Cassandra for GPU based processing, so reading and writing data efficiently in large chunks is of paramount importance to me. :)

@hjarraya

I am not sure if it's fixed. It's still volatile, I was able to reproduce the error

DEBUG 14:57:17,718 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 val
ues at consistency ONE
DEBUG 14:57:17,719 request complete
DEBUG 14:57:17,719 Responding: EMPTY RESULT
DEBUG 14:57:17,721 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 val
ues at consistency ONE
DEBUG 14:57:17,722 request complete
DEBUG 14:57:17,722 Responding: EMPTY RESULT
DEBUG 14:57:17,725 Received: EXECUTE f7080daad4b908a71d1d416359be3469 with 2 val
ues at consistency ONE
DEBUG 14:57:17,726 request complete
DEBUG 14:57:17,726 Responding: EMPTY RESULT
ERROR 14:57:19,480 Unexpected exception during request
java.io.IOException: An existing connection was forcibly closed by the remote ho
st
        at sun.nio.ch.SocketDispatcher.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198)
        at sun.nio.ch.IOUtil.read(IOUtil.java:166)
        at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:245)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:59)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedK
eys(AbstractNioWorker.java:472)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioW
orker.java:333)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
        at java.lang.Thread.run(Thread.java:662)
DEBUG 14:57:25,633 Disseminating load info ...
DEBUG 14:58:25,639 Disseminating load info ...
@ananthonline ananthonline reopened this Jan 16, 2013
@ananthonline

Oh, I see - I'm unable to repro it now. I would appreciate a Nuget package with the latest update even if you do mark this a partial fix.

@pchalamet
Owner
@pchalamet
Owner

2.1.2 is available. Tell me if the issue is (at least !) fixed !

@ananthonline

Like I said - I cannot repro the issue anymore, but I reopened this issue because @hjarraya commented he still saw it. I will continue to work with 2.1.2 and report back if I see this happen again.

@pchalamet
Owner
@hjarraya
@ananthonline

I saw the error on the Cassandra side as well, but assumed that was due to the connection being terminated at the server when we invoke ClusterManager.Shutdown. I don't see any issues on the .NET side anymore.

@pchalamet
Owner

Yes Cassandra does log client disconnect. I'm closing this then. If any trouble, reopen it with a callstack !
Thanks.

@pchalamet pchalamet closed this Jan 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.