Hi there -
Is there a setting of storage config or some other *user-level* programmatic
means that would cause Cassandra not to write to disk?
\
- m.
cked the code in this case.)
It would be good if this level was possible to set in the CLI at least for
"gets" ...
- m.
On Thu, Feb 25, 2010 at 11:12 AM, Jonathan Ellis wrote:
> How about the debug output?
>
> On Thu, Feb 25, 2010 at 12:03 PM, Masood Mortazavi
>
t_slice"
> ?
>
> On Thu, Feb 25, 2010 at 1:35 AM, Masood Mortazavi
> wrote:
> > Besides what I just said below, I should have also added that in the
> > scenario discussed here:
> >
> > While RackUnawareStrategy is used ...
> >
> > Node B which
>From the code, it appears that for "get" the default is ONE.
Column column = thriftClient_.get(tableName, key, path,
ConsistencyLevel.ONE).column
- m.
On Thu, Feb 25, 2010 at 11:08 AM, Masood Mortazavi <
masoodmortaz...@gmail.com> wrote:
>
>
> What is the write an
What is the write and read consistency level for the CLI tool
"cassandra-cli" ?
Do the "set" and "get" commands in the "cli" allow the Consistency Level to
be specified for a given "set" or "get"?
Is there a current specification of CLI anywhere on the wiki?
( How are JIRA's related to the CLI t
Feb 24, 2010 at 11:18 PM, Masood Mortazavi <
masoodmortaz...@gmail.com> wrote:
> Yes.
> Identical with replication factor of 2.
> m.
>
>
> On Wed, Feb 24, 2010 at 8:33 PM, Jonathan Ellis wrote:
>
>> Is the configuration identical on all nodes? Specifically, is
>&g
On Wed, Feb 24, 2010 at 8:29 PM, Jonathan Ellis wrote:
> On Wed, Feb 24, 2010 at 9:29 PM, Masood Mortazavi
> wrote:
> > Is there a configuration and step-by-step *procedure* for production
> > deployments of Cassandra?
>
> Not really. As w/ any cluster deployment, som
Yes.
Identical with replication factor of 2.
m.
On Wed, Feb 24, 2010 at 8:33 PM, Jonathan Ellis wrote:
> Is the configuration identical on all nodes? Specifically, is
> ReplicationFactor set to 2 on all nodes?
>
> On Wed, Feb 24, 2010 at 10:07 PM, Masood Mortazavi
> wrote:
I wonder if anyone can provide an explanation for the following behavior
observed in a three-node cluster:
1. In a three-node (A, B and C) installation, I use the cli, connected to
node A, to set 10 data items.
2. On cli connected to node A, I do get, and can see all 10 data items.
3. I take nod
Is there a configuration and step-by-step *procedure* for production
deployments of Cassandra?
By the way, I've noticed that not all potentially configurable setting may
actually be included in the -- storage-config.xml -- that's distributed with
the releases. [For example, there seems to be some
10 matches
Mail list logo
