You might consider writing some kind of php script that runs nodetool
"ring" and parse the output?
2012/2/6 Tamil selvan R.S
> Hi,
> What is the best way to know the cluster status via php?
> Currently we are trying to connect to individual cassandra instance with
> a specified timeout and if
Do you allow both outbound as inbound traffic? You might also try allowing
both TCP as UDP.
2012/2/6 Roshan
> Yes, If the firewall is disable it works.
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/nodetool-hangs-and-didn-t-print-anythi
Tamil, what is the underlying purpose you are trying to achieve? To
have your webpages know and detect when a node is down? To have a
monitoring tool detect when a node is down? PHPCassa allows you to
define multiple nodes. If one node is down, it should log information
to the webserver logs an
I need a database to log and retrieve sensor data.
Is cassandra the right solution for this task and if, how should I
set it up and which access methods should I use?
If not, which other DB system might be a better fit?
The details are as follows:
Glossary
- Node = A computer on wh
Aaron,
Have reduced cache sizes and been monitoring for the past week. It appears as
if this was the culprit - since the changes have not seen a resurfacing.
For those keeping score at home.
* Had sudden persistent spikes in CPU from the Cassandra java process
* Occurred every 24-48 hours an
As far as I'm familiar with Cassandra, I gave my opinion for every
requirement on your list:
1) 10k inserts / seconds should be no problem at all for Cassandra
2) Cassandra should scale to that
3) As the homepage of Cassandra states that amount of data should be able
to fit (source: http://cassan
On Sat, Feb 4, 2012 at 8:54 PM, Yiming Sun wrote:
> Interesting idea, Jim. Is there a reason you don't you use
> "metadata:{accountId}" instead? For performance reasons?
No, because the column comparator is defined as
CompositeType(DateType, AsciiType), and all column names must conform
to that
JMX is not very firewall friendly. The problem is that JMX is a two
connection process. The first connection happens on port 7199 and the
second connection happens on some random port > 1024. Work on changing
this behavior was started in this ticket:
https://issues.apache.org/jira/browse/CASSANDRA
Thanks for the clarification, Jim. I didn't know the first comparator was
defined as DateType. Yeah, in that case, the beginning of the epoch is the
only choice.
-- Y.
On Mon, Feb 6, 2012 at 11:35 AM, Jim Ancona wrote:
> On Sat, Feb 4, 2012 at 8:54 PM, Yiming Sun wrote:
> > Interesting idea,
That looks like a bug. Were you writing counters ?
Can you please add it here https://issues.apache.org/jira/browse/CASSANDRA ,
include some information on the request that caused it and email the bug report
back to the list.
(note to self) I *think* the problem is the counter WritePerformer
Sounds like a good start. Super columns are not a great fit for modeling time
series data for a few reasons, here is one
http://wiki.apache.org/cassandra/CassandraLimitations
It's also a good idea to partition time series data so that the rows do not
grow too big. You can have 2 billion columns
On Sat, Feb 4, 2012 at 7:03 AM, Jonathan Ellis wrote:
> Sounds like you need to increase sysctl vm.max_map_count
This did not work. I increased vm.max_map_count from 65536 to 131072.
I am still getting the same error.
ERROR [SSTableBatchOpen:4] 2012-02-06 11:43:50,463
AbstractCassandraDaemon.jav
On Mon, Feb 6, 2012 at 11:50 AM, Ajeet Grewal wrote:
> On Sat, Feb 4, 2012 at 7:03 AM, Jonathan Ellis wrote:
>> Sounds like you need to increase sysctl vm.max_map_count
>
> This did not work. I increased vm.max_map_count from 65536 to 131072.
> I am still getting the same error.
The number of fi
Here are the last few lines of strace (of one of the threads). There
are a bunch of mmap system calls. Notice the last mmap call a couple
of lines before the trace ends. Could the last mmap call fail?
== BEGIN STRACE ==
mmap(NULL, 2147487599, PROT_READ, MAP_SHARED, 37, 0xbb000) = 0x7709b54000
Hi All,
We are happy to announce release of Kundera 2.0.5.
Kundera is a JPA 2.0 based, Object-Datastore Mapping Library for NoSQL
Datastores. The idea behind Kundera is to make working with NoSQL Databases
drop-dead simple and fun. It currently supports Cassandra, HBase,
MongoDB and relational da
> It's also a good idea to partition time series data so that the rows do not
> grow too big. You can have 2 billion columns in a row, but big rows have
> operational down sides.
What are the down sides here? Unfortunately I have an existing system
which I modeled with large rows (because I use th
On Tue, Feb 7, 2012 at 6:39 AM, aaron morton wrote:
> Sounds like a good start. Super columns are not a great fit for modeling
> time series data for a few reasons, here is one
> http://wiki.apache.org/cassandra/CassandraLimitations
>
None of those jump out at me as horrible for my case. If I mo
17 matches
Mail list logo
