No, at least not at the default logging level. However, we have solved
the problem by checking out the latest revision of Thrift from the
official repository, so it seems that it was not Cassandra's problem.
On 07/29/2011 10:13 PM, ruslan usifov wrote:
Do you have any error messages in cassand
Having 2056 live SSTables is very odd. Minor compaction should automatically
reduce that number. What settings for min_compaction_threshold and
max_compaction_threshold did you use when creating the CF ?
You can check them with node tool getcompactionthreshold . The default is min 4
and max 32
Upgrade at least to 0.8.1 as your version has broken compaction...
Reagards
Wojtek Meler
- Reply message -
Od: "myreasoner"
Data: pon., sie 1, 2011 04:23
Temat: Read latency is over 1 minute on a column family with 400,000 rows
Do: "cassandra-u...@incubator.apache.org"
Hi, my read late
On Fri, Jul 29, 2011 at 12:02 PM, Chris Burroughs
wrote:
> On 07/25/2011 01:53 PM, Ryan King wrote:
>> Actually I was wrong– our patch will disable gosisp and thrift but
>> leave the process running:
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-2118
>>
>> If people are interested in that
It was set the min/4 max/32
Current compaction thresholds for MyKeyspace/Fingerprint:
min = 4, max = 32
What could possibly cause cassandra to ignore these settings?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Read-latency-is-over-1-minute
Why do you think it's ignoring it?
In the output you pasted it said "I'm currently busy with a compaction
and I have a backlog of 66 more to get to after that."
On Mon, Aug 1, 2011 at 1:51 PM, myreasoner wrote:
> It was set the min/4 max/32
>
> Current compaction thresholds for MyKeyspace/Finger
All compaction related settings in the yaml were untouched. The fingerprint
column family has been populated three days ago and the cpu/disk usage were
pretty low. I'd think Cassandra will silently start the compaction thread
on my behalf and try to preserve the min/max thresholds, rather than wa
You really need to upgrade from 0.8.0 to fix that. Restarting won't
help, much (you'll get exactly one compaction against a given sstable,
before it stops working again).
On Mon, Aug 1, 2011 at 2:34 PM, myreasoner wrote:
> All compaction related settings in the yaml were untouched. The fingerpr
Thanks. I will upgrade to 0.8.1 then.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Read-latency-is-over-1-minute-on-a-column-family-with-400-000-rows-tp6639649p6642582.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive
Incase you missed it, fresh off the press
http://www.datastax.com/dev/blog/bulk-loading
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 30 Jul 2011, at 04:10, Jeff Schmidt wrote:
> Hello:
>
> I'm relatively new to Cassandra, but
for example my data consists of "salary", "office stationery list",
let's say I do use the same replicationStrategy for them, these 2
data sets have
different key ranges, key distributions,
then is it better to use separate keyspaces for each of them? or use a
single one?
the factors I can thin
Dear all,
I'm always meeting mp with schema disagree problems while trying to create a
column family like this, using cassandra-cli:
create column family sd
with column_type = 'Super'
and key_validation_class = 'UUIDType'
and comparator = 'LongType'
and subcomparator = 'UTF8Type
I thought the schema disagree problem was already solved in 0.8.1...
On possible solution is to decommission the disagree node and rejoin it.
On Tue, Aug 2, 2011 at 8:01 AM, Yi Yang wrote:
> Dear all,
>
> I'm always meeting mp with schema disagree problems while trying to create
> a column fam
On Mon, Aug 1, 2011 at 6:08 PM, Yang wrote:
> for example my data consists of "salary", "office stationery list",
>
> let's say I do use the same replicationStrategy for them, these 2
> data sets have
> different key ranges, key distributions,
>
> then is it better to use separate keyspaces for
I have just started with a cassandra, so maybe a simple configuration problem?
from a java program, with consistency level set to ANY,
Exception in thread "main" UnavailableException()
at
org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:19053)
at
org
Hi Jonathan,
AFAIK, you might change the internal implementation of super column family
by using the composite column. Does this mean that maybe the secondary index
will be supported on super columns in the future? will you use composite
column to add more capability to super column family or we a
All:
I compile the cassandra source code by ant. The following error print:
BUILD FAILED
E:\work\research\cassandra\apache-cassandra-0.6.3-src\apache-cassandra-0
.6.3-src
\build.xml:170: taskdef A class needed by class
com.thoughtworks.paranamer.ant.P
aranamerGeneratorTask cannot be foun
To the best of my ability to predict the future, we would probably
enhance "native" composite columns with those features, but not expose
them in the old supercolumn API.
So again, if supercolumns work for you, we won't pull the rug out from
under you, but don't start using them expecting them to
All:
I use ant to compile cassandra. It is failure on ivy download, error
is “Connection refused”, but I can get it from ie. So I download it and put in
on dir /build. Then I compile again, it is blocked on ivy dependency download.
I download the apache-rat-0.6.jar, commons-logging-1.1
19 matches
Mail list logo
