Good call! Java client was using Cassandra 2.11 lib jars in classpath.
Switching to Cassandra 3.11 jars in Java client classpath works!
Thx!
Lou.
On Thu, Apr 26, 2018 at 10:30 AM, Michael Shuler
wrote:
> On 04/26/2018 09:17 AM, Lou DeGenaro wrote:
> >
> > I started fresh and edited the 3.11 ca
On 04/26/2018 09:17 AM, Lou DeGenaro wrote:
>
> I started fresh and edited the 3.11 cassandra.yaml file. Here are the
> exact changes:
>
> diff cassandra.yaml cassandra.yaml.orig
> 425c425
> < - seeds: "bluej421"
> ---
>> - seeds: "127.0.0.1"
> 599c599
> < listen_address: blu
I did not realize that the 3.0.9 cassandra.yaml file is not compatible with
3.11??
I started fresh and edited the 3.11 cassandra.yaml file. Here are the
exact changes:
diff cassandra.yaml cassandra.yaml.orig
425c425
< - seeds: "bluej421"
---
> - seeds: "127.0.0.1"
599c599
< l
On 04/26/2018 09:03 AM, Michael Shuler wrote:
> Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
> earlier version, which used schema_columnfamilies, I think?
Similar error on:
https://datastax-oss.atlassian.net/browse/JAVA-1092
--
Michael
---
OK, thanks for the extra info.
Hmm.. `unconfigured table schema_keyspaces`
Seems like an incomplete upgrade to 3.0.9 (and now 3.11.2) from some
earlier version, which used schema_columnfamilies, I think?
--
Michael
On 04/26/2018 08:55 AM, Lou DeGenaro wrote:
> Sorry, my mistake. Everything is
Sorry, my mistake. Everything is bluej421. I tried to (but in hind sight
should not have) edit the append to make the host more generic. The actual
experiment uses bluej421 everywhere.
cqlsh from the same host works fine with the same exact host specified as
CQLSH_HOST.
I just now installed a
host421 != bluej421
My guess is 192.168.3.232 != {host421,bluej421} somewhere.
If DNS hostnames are being used, the DNS infrastructure needs to be spot
on, forward and reverse. If the DNS infrastructure is /etc/hosts, those
hosts entries need to be spot on for the entire cluster, forward and
rever
