Tim, you can restart a node in decommission mode, after that, I will start
as a normal node. But it will be nice to have a tool to do that.
On Wed, Feb 20, 2019 at 2:32 PM Timothy Palpant wrote:
> Hi!
>
> I was wondering if it is possible to abort/cancel a decommission that was
> initiated with
es + compaction strategies
> or it was changed somehow?
>
>
> Best,
>
> Kyrill
>
> --
> *From:* Dikang Gu
> *Sent:* Monday, March 5, 2018 8:26 PM
> *To:* d...@cassandra.apache.org; cassandra
> *Subject:* Rocksandra blog post
>
> As some of you already kno
As some of you already know, Instagram Cassandra team is working on the
project to use RocksDB as Cassandra's storage engine.
Today, we just published a blog post about the work we have done, and more
excitingly, we published the benchmark metrics in AWS environment.
Check it out here:
https://en
What's the C* version do you use? Sounds like the secondary index is very
out of sync with the parent cf.
On Fri, Mar 2, 2018 at 6:23 AM, Malte Krüger
wrote:
> hi,
>
> we have an CF which is about 2 gb in size, it has a seondary index on one
> field (UUID).
>
> the index has a size on disk of ab
What's the partitioner you use? We have logic to prevent duplicate tokens.
private static Collection adjustForCrossDatacenterClashes(final
TokenMetadata tokenMetadata,
StrategyAdapter strategy, Collection tokens)
{
List filtered = Lists.newArrayListWithCapacity(tokens.size());
for (Token
I fixed the new allocation algorithm in non bootstrap case,
https://issues.apache.org/jira/browse/CASSANDRA-13080?filter=-2, the fix is
in 3.12+, but not in 3.0.
On Wed, Jan 24, 2018 at 9:32 AM, Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Thu, Jan 18, 2018 at 5:19 AM, kurt grea
Do you have some detailed benchmark metrics? Like the QPS, Avg read/write
latency, P95/P99 read/write latency?
On Fri, Jan 5, 2018 at 5:57 PM, Justin Sanciangco
wrote:
> I am benchmarking with the YCSB tool doing 1k writes.
>
>
>
> Below are my server specs
>
> 2 sockets
>
> 12 core hyperthreade
@Peng, how many network interfaces do you have on your machine? If you just
have one NIC, you probably need to wait this storage port patch.
https://issues.apache.org/jira/browse/CASSANDRA-7544 .
On Thu, Dec 7, 2017 at 7:01 AM, Oliver Ruebenacker wrote:
>
> Hello,
>
> Yes, you can.
>
>
What's the compaction strategy are you using? level compaction or size
tiered compaction?
On Fri, Oct 13, 2017 at 4:31 PM, Bruce Tietjen <
bruce.tiet...@imatsolutions.com> wrote:
> I hadn't noticed that is is now attempting two impossible compactions:
>
>
> id co
I will try the fixes, thanks Benjamin & Jeff.
On Thu, Sep 21, 2017 at 8:55 PM, Jeff Jirsa wrote:
> https://issues.apache.org/jira/plugins/servlet/mobile#
> issue/CASSANDRA-11995
>
>
>
> --
> Jeff Jirsa
>
>
> On Sep 19, 2017, at 4:36 PM, Dikang Gu wrote:
>
&
Hi Peng,
C* periodically saves cache to disk, to solve cold start problem. If
row_cache_save_period=0, it means C* does not save cache to disk. But the
cache is still working, if it's enabled in table schema, just the cache
will be empty after restart.
--Dikang.
On Tue, Sep 19, 2017 at 8:27 PM,
Hello,
In our production cluster, we had multiple times that after a *unclean*
shutdown, cassandra sever can not start due to commit log exceptions:
2017-09-17_06:06:32.49830 ERROR 06:06:32 [main]: Exiting due to error while
processing commit log during initialization.
2017-09-17_06:06:32.49831
o
To me, CL.TWO and CL.THREE are more like work around of the problem, for
example, they do not work if the number of replicas go to 8, which does
possible in our environment (2 replicas in each of 4 DCs).
What people want from quorum is strong consistency guarantee, as long as
R+W > N, there are th
2017 at 7:47 PM, Jonathan Haddad wrote:
> It would be a little weird to change the definition of QUORUM, which means
> majority, to mean something other than majority for a single use case.
> Sounds like you want to introduce a new CL, HALF.
> On Thu, Jun 8, 2017 at 7:43 PM
dd
> additional nodes in the future this would obviously no longer work. Also
> the benefit of this is dubious, since 3/4 nodes still need to be accessible
> to perform writes. I'd also guess that it's unlikely to provide any
> significant performance increase.
>
> Justi
Hello there,
We have some use cases are doing consistent read/write requests, and we
have 4 replicas in that cluster, according to our setup.
What's interesting to me is that, for both read and write quorum requests,
they are blocked for 4/2+1 = 3 replicas, so we are accessing 3 (for write)
+ 3 (
1. The coordinator still store system data and hints, but they should not
store any user data since they are not part of ring.
2. We are using coordinator for thrift client. For cql based drivers, they
needs to talk to nodes in the ring, so I think coordinator mode won't work
for them.
-Dikang
On
11:09 PM, Jeff Jirsa wrote:
>
>
> On 2017-04-18 18:57 (-0700), Dikang Gu wrote:
> > Hello there,
> >
> > We are upgrading one of our cluster from 2.1.14 to 2.2.5, but cassandra
> had
> > problems replaying the commit logs...
> >
> > Her
Hello there,
We are upgrading one of our cluster from 2.1.14 to 2.2.5, but cassandra had
problems replaying the commit logs...
Here is the exception, does anyone experience similar before?
2017-04-19_00:22:21.69943 DEBUG 00:22:21 [main]: Finished reading
/data/cassandra/commitlog/CommitLog-4-148
Have you run 'nodetool rebuild dc_india' on the new nodes?
On Tue, Jan 24, 2017 at 7:51 AM, Benjamin Roth
wrote:
> Have you also altered RF of system_distributed as stated in the tutorial?
>
> 2017-01-24 16:45 GMT+01:00 Abhishek Kumar Maheshwari timesinternet.in>:
>
>> My Mistake,
>>
>>
>>
>> B
Btw, the C* version is 2.2.5, with several backported patches.
On Sun, Jan 22, 2017 at 10:36 PM, Dikang Gu wrote:
> Hello there,
>
> We have a 100 nodes ish cluster, I find that there are dropped messages on
> random nodes in the cluster, which caused error spikes and P99 latency
Hello there,
We have a 100 nodes ish cluster, I find that there are dropped messages on
random nodes in the cluster, which caused error spikes and P99 latency
spikes as well.
I tried to figure out the cause. I do not see any obvious bottleneck in the
cluster, the C* nodes still have plenty of cpu
Hi guys,
Sometimes we need to replace multiple hosts in the same rack, is it safe to
replace them in parallel, using the replace-node command?
Will it cause any data inconsistency if we do so?
Thanks
Dikang.
--
Dikang
> gossip debug logs of replacement and other nodes, and if the replacement
> node had the same or different ip as the original node since they are
> slightly different code paths after #8523).
>
> 2016-11-18 19:07 GMT-02:00 Dikang Gu :
>
>> Paulo, the tokens field for 2401:d
ndpoint /2401:db00:2130:4091:
> face:0:13:0 ? Does it contain the TOKENS attribute? If it's missing, is
> it only missing on this node or other nodes as well?
>
> 2016-11-18 17:02 GMT-02:00 Dikang Gu :
>
>> Hi, I encountered couple times that I could not replace a down node
Hi, I encountered couple times that I could not replace a down node due to
error:
2016-11-17_19:33:58.70075 Exception (java.lang.RuntimeException)
encountered during startup: Could not find tokens for
/2401:db00:2130:4091:face:0:13:0 to replace
2016-11-17_19:33:58.70489 ERROR 19:33:58 [main]: Exce
s deploying 2.1 -- so i'm not sure how "hacky" it is if it
> works..
>
> best,
> kjellman
>
>
> On Nov 8, 2016, at 11:31 AM, Dikang Gu mailto:dik
> an...@gmail.com>> wrote:
>
> This is very expensive:
>
> "MessagingService-Incoming-/2401:
Hi Simon,
For a 10 nodes cluster, Cassandra nodetool should be enough for most C*
operations and maintenance, unless you have some special requirements.
For the memory, you can check what's your JVM settings, and the gc log for
JVM usage.
--Dikang.
On Mon, Nov 7, 2016 at 7:25 PM, wxn...@zjqunsh
Agree, change the last_time to be descending order will help, you can also
TTL the data, so that the old records will be purged by Cassandra.
--Dikang.
On Mon, Nov 7, 2016 at 10:39 PM, Alain Rastoul
wrote:
> On 11/08/2016 03:54 AM, ben ben wrote:
>
>> Hi guys,
>>CREATE TABLE recent (
>>
We are seeing huge cpu regression when upgrading one of our 2.0.16 cluster
to 2.1.14 as well. The 2.1.14 node is not able to handle the same amount of
read traffic as the 2.0.16 node, actually, it's less than 50%.
And in the perf results, the first line could go as high as 50%, as we turn
up the r
Hi Aleksey, do you get a chance to take a look?
Thanks
Dikang.
On Thu, Mar 24, 2016 at 10:30 PM, Dikang Gu wrote:
> @Aleksey, sure, here is the jira:
> https://issues.apache.org/jira/browse/CASSANDRA-11432
>
> Thanks!
>
> On Thu, Mar 24, 2016 at 5:32 PM, Aleksey Yeschenko
@Aleksey, sure, here is the jira:
https://issues.apache.org/jira/browse/CASSANDRA-11432
Thanks!
On Thu, Mar 24, 2016 at 5:32 PM, Aleksey Yeschenko
wrote:
> Best open a JIRA ticket and I’ll have a look at what could be the reason.
>
> --
> AY
>
> On 24 March 2016 at 23:20:55
n 24 March 2016 at 06:17:27, Dikang Gu (dikan...@gmail.com) wrote:
>
> Hello there,
>
> We are experimenting Counters in Cassandra 2.2.5. Our setup is that we
> have
> 6 nodes, across three different regions, and in each region, the
> replication factor is 2. Basically, each nodes
ly apps try to issue requests to a local data
> center for performance. Having to ping all data centers on all requests to
> achieve a quorum seems a bit excessive.
>
> Can you advise us on your thinking when you selected RF=2?
>
>
> -- Jack Krupansky
>
> On Thu, Mar 24,
Hello there,
We are experimenting Counters in Cassandra 2.2.5. Our setup is that we have
6 nodes, across three different regions, and in each region, the
replication factor is 2. Basically, each nodes holds a full copy of the
data.
When are doing 30k/s counter increment/decrement per node, and at
>> Matt Kennedy
>>
>> Sr. Product Manager, DSE Core
>>
>> matt.kenn...@datastax.com | Public Calendar <http://goo.gl/4Ui04Z>
>>
>> *DataStax Enterprise - the database for cloud applications.*
>>
>> On Thu, Mar 10, 2016 at 11:44 AM, Dikang Gu
Fyi, this is the jira, https://issues.apache.org/jira/browse/CASSANDRA-11348
.
We can move the discussion to the jira if want.
On Thu, Mar 17, 2016 at 11:46 AM, Dikang Gu wrote:
> Hi Eric,
>
> Thanks for sharing the information!
>
> We also mainly want to use it for trimming
st it out, I'd love to hear from you.
>
> On Sat, Mar 12, 2016 at 5:12 AM Marcus Eriksson wrote:
>
>> We don't have anything like that, do you have a specific use case in mind?
>>
>> Could you create a JIRA ticket and we can discuss there?
>>
>> /Mar
Hello there,
RocksDB has the feature called "Compaction Filter" to allow application to
modify/delete a key-value during the background compaction.
https://github.com/facebook/rocksdb/blob/v4.1/include/rocksdb/options.h#L201-L226
I'm wondering is there a plan/value to add this into C* as well? Or
I think I would probably give it a try using
>>> CCM (
>>> > https://github.com/pcmanus/ccm) or some test cluster with 'production
>>> > like'
>>> > setting and schema. You can write a row, flush it and see how big is
>>> the
>>> &
Hello there,
I'm wondering is there a good way to measure the write amplification of
Cassandra?
I'm thinking it could be calculated by (size of mutations written to the
node)/(number of bytes written to the disk).
Do we already have the metrics of "size of mutations written to the node"?
I did n
Hi there,
I have a cluster which has a lot of counter updates. My question is that
when I run the `nodetool tpstats`, I see a lot of MutationStage actions but
no CounterMutationStage stats. I'm wondering is it normal or is it
something I should worry about?
I'm using Cassandra 2.1.8 and the C dri
Hi there,
In the datastax java driver, do I have to use the cql to talk to cassandra
cluster?
Can I still use thrift interface to talk to cassandra? Any reason that we
should not use thrift anymore?
Thanks.
--
Dikang
0.0.0:9042 :::*
LISTEN 2411582/java
So using the sever ip "2401:db00:11:60ed:face:0:31:0", I can connect to the
thrift port 9160, but not the native port 9042. Do you know the reason for
this?
Thanks
Dikang.
On Wed, Nov 4, 2015 at 12:29 PM, Michael Shuler
wrote:
> On 11/04/2
Hi there,
Right now, it seems if I add a contact point like this:
cluster = Cluster.builder().addContactPoint().build();
When client is connected to the cluster, client will fetch the addresses
for all the nodes in the cluster, and try to connect to them.
I'm wondering can I disable the behavio
Hi there,
I have ipv6 only cassandra cluster, and I'm trying to connect to it using
java driver, like:
Inet6Address inet6 = (Inet6Address)
InetAddress.getByName("2401:db00:0011:60ed:face::0031:");
cluster = Cluster.builder().addContactPointsWithPorts(Arrays.asList(new
InetSocketAddress(in
The NPE throws when node tried to handleStateLeft, because it can not find
the tokens associated with the node, can we just ignore the NPE and
continue to remove the endpoint from the ring?
On Fri, Sep 25, 2015 at 10:52 AM, Dikang Gu wrote:
> @Jeff, yeah, I run the nodetool grep, and in my c
onsistencies you’re
>> not yet aware of (for example, if you expect that you have 100 nodes in the
>> cluster, I’m betting that the query above returns 99 on at least one of the
>> nodes). If this is the case, please reply so that you and I can submit a
>> Jira and comp
eEndpoint, to which host are you connected,
> and what argument are you passing?
>
> Are there other nodes in the ring that you’re not including in the
> ‘nodetool status’ output?
>
>
> From: Dikang Gu
> Reply-To: "user@cassandra.apache.org"
> Date: Tuesday, Septe
ping.
On Mon, Sep 21, 2015 at 11:51 AM, Dikang Gu wrote:
> I have tried all of them, neither of them worked.
> 1. decommission: the host had hardware issue, and I can not connect to it.
> 2. remove, there is not HostID, so the removenode did not work.
> 3. unsafeAssassinateEndpo
, Sep 21, 2015 at 11:11 AM, Sebastian Estevez <
sebastian.este...@datastax.com> wrote:
> Order is decommission, remove, assassinate.
>
> Which have you tried?
> On Sep 21, 2015 10:47 AM, "Dikang Gu" wrote:
>
>> Hi there,
>>
>> I have a dead node in o
Hi there,
I have a dead node in our cluster, which is a wired state right now, and
can not be removed from cluster.
The nodestatus shows:
Datacenter: DC1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens OwnsHost ID
Hi guys,
We have some issues with streaming in 2.1.2. We find that there are a lot
of patches in 2.1.5. Is it ready for upgrade?
Thanks.
--
Dikang
Dikang.
On Mon, Apr 20, 2015 at 6:48 PM, Robert Coli wrote:
> On Mon, Apr 20, 2015 at 6:08 PM, Dikang Gu wrote:
>
>> When I bring in a new node into the cluster, it introduces significant
>> load to the cluster. For the new node, the cpu usage is 100%, but disk
>> write io
Hi guys,
We have a 100+ nodes cluster, each node has about 400G data, and is running
on a flash disk. We are running 2.1.2.
When I bring in a new node into the cluster, it introduces significant load
to the cluster. For the new node, the cpu usage is 100%, but disk write io
is only around 50MB/s,
t;>>
> >>>> That's all folks!
> >>>>
> >>>> [1]: http://goo.gl/t3qpw (CHANGES.txt)
> >>>> [2]: http://goo.gl/6t0qN (NEWS.txt)
> >>>> [3]: http://wiki.apache.org/cassandra/DebianPackaging
> >>>> [4]:
> >>>>
> http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-0-compression
> >>>> [5]:
> >>>>
> http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-0-improved-memory-and-disk-space-management
> >>>> [6]:
> >>>>
> http://www.datastax.com/dev/blog/leveled-compaction-in-apache-cassandra
> >>>> [7]:
> >>>>
> http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-0-performance
> >>>> [8]:
> >>>>
> http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-0-windows-service-new-cql-clients-and-more
> >>>> [9]: http://acunu.com/blogs/eric-evans/cassandra-drivers-released/
> >>>>
> >>>
> >>>
> >>> --
> >>> Jonathan Ellis
> >>> Project Chair, Apache Cassandra
> >>> co-founder of DataStax, the source for professional Cassandra support
> >>> http://www.datastax.com
> >>>
> >
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>
--
Dikang Gu
0086 - 18611140205
(WrappedRunnable.java:30)
... 3 more
Thanks.
--
Dikang Gu
0086 - 18611140205
ot; on node1, it shows node2 unreachable:
>>> Cluster Information:
>>>Snitch: org.apache.cassandra.locator.SimpleSnitch
>>>Partitioner: org.apache.cassandra.dht.RandomPartitioner
>>>Schema versions:
>>> UNREACHABLE: [node2]
>>> 05f1ee3b-e063-11e0-97d5-63c2fb3f0ca8: [node1, node3]
>>>
>>> node3 seems act normal.
>>>
>>>
>>> I saw the JMXPORT has changed since 0.8, is that the reason node was
>>> unreachable?
>>>
>>>
>>> thanks!
>>>
>>>
>>>
>>
>
--
Dikang Gu
0086 - 18611140205
7)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at
org.apache.cassandra.db.ColumnFamilyStore.(ColumnFamilyStore.java:311)
... 9 more
Thanks.
--
Dikang Gu
0086 - 18611140205
version is a maintenance/bug fix release[1]. Please pay attention to
> the
> release notes[2] before upgrading and let us know[3] if you were to
> encounter
> any problem.
>
> Have fun!
>
>
> [1]: http://goo.gl/A5YmF (CHANGES.txt)
> [2]: http://goo.gl/J5Iix (NEWS
s
version mismatch. cannot apply.
--
Dikang Gu
0086 - 18611140205
On Wednesday, August 10, 2011 at 11:35 AM, Dikang Gu wrote:
> Hi Aaron,
>
> I set the log level to be DEBUG, and find a lot of forceFlush debug info in
> the log:
>
> DEBUG [StreamStage:1] 2011-08-10 11:31:5
clean
What does this mean?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Wednesday, August 10, 2011 at 6:42 AM, aaron morton wrote:
> um. There has got to be something stopping the migration from completing.
>
> Turn the logging up to DEBUG before starting and look for mess
: true
Could you explain this?
If I change the token given to 1.27 to another one, will it help?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Sunday, August 7, 2011 at 4:14 PM, aaron morton wrote:
> did you check the logs in 1.27 for errors ?
>
> Could you be seeing this ?
veloper
> @aaronmorton
> http://www.thelastpickle.com
>
> On 5 Aug 2011, at 12:46, Dikang Gu wrote:
>
> Sure, I can find the stack trace for some exceptions:
>
> ERROR [pool-2-thread-132] 2011-07-23 13:29:04,869 Cassandra.java (line
> 3210) Internal error processing get_ra
logs that shows Leaving?
>> >
>> > --
>> > View this message in context:
>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/move-one-node-for-load-re-balancing-then-it-status-stuck-at-Leaving-tp6655168p6655326.html
>> > Sent from the cassandra-u...@incubator.apache.org mailing list archive
>> at Nabble.com.
>> >
>>
>
>
--
Dikang Gu
0086 - 18611140205
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 6 Aug 2011, at 22:56, Dikang Gu wrote:
>
> I have tried this, but the schema still does not agree in the cluster:
>
> [default@unknown] describe cluster;
> Cluster Informat
Perroud wrote:
> Based on http://wiki.apache.org/cassandra/FAQ#schema_disagreement,
> 75eece10-bf48-11e0--4d205df954a7 own the majority, so shutdown and
> remove the schema* and migration* sstables from both 192.168.1.28 and
> 192.168.1.27
>
>
> 2011/8/5 Dikang Gu :
, 192.168.1.25]
06da9aa0-bda8-11e0--9510c23fceff: [192.168.1.27]
three different schema versions in the cluster...
--
Dikang Gu
0086 - 18611140205
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 4 Aug 2011, at 15:26, Dikang Gu wrote:
>
> Yes, I do find the error log!
>
> ERROR [pool-2-thread-63] 2011-08-04 13:23:54,138 Cassandra.java (line 3210)
Yes, I do find the error log!
ERROR [pool-2-thread-63] 2011-08-04 13:23:54,138 Cassandra.java (line 3210)
Internal error processing get_range_slices
java.lang.NullPointerException
I'm using the cassandra-0.8.1, is this a known bug?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Wedn
Hi,
Can the schema disagreement problem be avoided?
Thanks.
--
Dikang Gu
0086 - 18611140205
As per subject.
Thanks.
--
Dikang Gu
0086 - 18611140205
tions?
--
Dikang Gu
0086 - 18611140205
2.168.1.27]
UNREACHABLE: [192.168.1.25]
What's the "UNREACHABLE"?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Wednesday, August 3, 2011 at 11:28 AM, Jonathan Ellis wrote:
> Have you seen http://wiki.apache.org/cassandra/FAQ#schema_disagreement ?
>
> On Tue, Aug 2, 2011 at 10:2
(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
What does this mean?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Tuesday, August 2, 2011 at 6:04 PM, aaron morton wrote:
> Hang on, using brain now.
>
> That is triggering a small bug in the code see
Is this a bug? Any ideas?
Thanks.
--
Dikang Gu
0086 - 18611140205
ame: 'splitvolume',
>validation_class : 'LongType'
>},{
>column_name: 'splitclose',
>validation_class : 'FloatType'
>}
>]
> ;
>
> I've tried to erase everything and restart Cassandra but this still
> happens. But when I clear the column_metadata section this no more
> disagreement error. Do you have any idea why this happens?
>
> Environment: 2 VMs, using the same harddrive, Cassandra 0.8.1, Ubuntu 10.04
> This is for testing only. We'll move to dedicated servers later.
>
> Best regards,
> Yi
>
--
Dikang Gu
0086 - 18611140205
Hi Aaron,
Thank you for your reply, I've reported a bug on the jira
https://issues.apache.org/jira/browse/CASSANDRA-2739 .
Since I'm not in the office now, so I will come up with more information and
try your methods when I'm in the office again, maybe next Monday.
Thanks.
--
(IncomingTcpConnection.java:155)
at
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:93)
Do you have any ideas about this?
Thanks.
--
Dikang Gu
0086 - 18611140205
Great! Congratulations!
--
Dikang Gu
0086 - 18611140205
On Friday, June 3, 2011 at 10:06 AM, aaron morton wrote:
> Big thanks to all the contributors and committers :)
>
> A
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> h
ype.LONGTYPE.getClassName());
columnFamilyDefinition.addColumnDefinition(bcdf);
cluster.updateColumnFamily(new ThriftCfDef(columnFamilyDefinition));
--
Dikang Gu
0086 - 18611140205
On Thursday, May 26, 2011 at 3:16 PM, aaron morton wrote:
> Please post to one list at a time. Otherwise
I want to build a secondary index on an existed column, how to programmatically
do this using hector API?
Thanks.
--
Dikang Gu
0086 - 18611140205
What's the naming convention of the column family in cassandra? I did not find
this in the wiki yet...
Thanks.
--
Dikang Gu
0086 - 18611140205
Thanks Aaron!
Through the commands "top" and "iostats", I find the IO system is not
overloaded yet. So I will check the data model.
And how to get the row size of a specific key? Do we have the api yet?
Thanks.
--
Dikang Gu
0086 - 18611140205
On Sunday, May 22, 2011 at 6
I use the default consistency level in the hector client, so it should be
QUORUM.
--
Dikang Gu
0086 - 18611140205
On Friday, May 20, 2011 at 4:25 PM, Jeffrey Kesselman wrote:
> What consistency are you asking for?
>
> On Fri, May 20, 2011 at 7:42 AM, Dikang Gu wrote:
> >
nodes? Any other options?
Thanks.
--
Dikang Gu
0086 - 18611140205
e
> with the disagreeing shema solved the issue.
>
>
> On Thu, May 5, 2011 at 12:40 AM, Dikang Gu wrote:
>
>> I got this exception when I was trying to create a new columnFamily using
>> hector api.
>>
>> me.prettyprint.hector.api.exceptions.HInvalidRequestException:
>
the disagreeing shema solved the issue.
>
>
> On Thu, May 5, 2011 at 12:40 AM, Dikang Gu wrote:
>
>> I got this exception when I was trying to create a new columnFamily using
>> hector api.
>>
>> me.prettyprint.hector.api.exceptions.HInvalidRequestException:
>>
cluster.
Thanks.
--
Dikang Gu
0086 - 18611140205
%
> 92535295865117307932921825928971026432
> 192.168.0.5 Up Normal 263.91 MB 12.28%
> 113427455640312821154458202477256070485
> 192.168.0.6 Up Normal 26.21 MB8.33%
> 127605887595351923798765477786913079296
>
--
Dikang Gu
0086 - 18611140205
? Normal 84.24 MB33.33%
56713727820156410577229101238628035242
10.18.101.213 Up Normal 54.44 MB33.33%
113427455640312821154458202477256070485
Is this correct? Why is the status "?" ?
Thanks.
On Tue, Apr 12, 2011 at 5:43 PM, Dikang Gu wrote:
> The 3 nodes were
/Operations#Range_changes
>
> http://wiki.apache.org/cassandra/Operations#Moving_or_Removing_nodes
>
> http://www.datastax.com/docs/0.7/operations/clustering#adding-capacity
>
>
>
> On Apr 12, 2011, at 11:00 AM, Dikang Gu wrote:
>
> > I have 3 cassandra 0.7.4 nodes in a cluster,
is there a way to
balance the three nodes?
Thanks.
--
Dikang Gu
0086 - 18611140205
93 matches
Mail list logo
