http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082 Software, Support, and Training for Apache Cassandra en-US Wed, 19 Jun 2013 07:15:20 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-521 Wed, 21 Sep 2011 15:41:37 +0000 gibrown 521@http://www.datastax.com/support-forums/ <p>I am running into similar problems due to trying to use CounterColumns which are only supported through Hadoop with cassandra 0.8.3+. I have tried replacing the jars:</p> <p>resources/cassandra/lib/apache-cassandra-0.8.1-brisk1-beta2.jar<br /> resources/cassandra/lib/apache-cassandra-thrift-0.8.1-brisk1-beta2.jar</p> <p>Tested by replacing with both 0.8.6 and 0.8.3. In both cases I did get the Pig demo (003) to run, but was unable to access my CounterColumns via Pig. </p> <p>Most relevant error seems to be: Failed to read data from "cassandra://SiteStats/views"</p> <p>Any ideas on what else I might need to upgrade. The next thing I am thinking of trying is rebuilding Brisk from source rather than just copying in the jars. Any tips?</p> <p>Thanks for any help you can provide.<br /> -Greg</p> <p>More background info:</p> <p>&gt;describe keyspace SiteStats<br /> Keyspace: SiteStats:<br /> Replication Strategy: org.apache.cassandra.locator.SimpleStrategy<br /> Durable Writes: true<br /> Options: [replication_factor:1]<br /> ColumnFamily: views<br /> Key Validation Class: org.apache.cassandra.db.marshal.BytesType<br /> Default column value validator: org.apache.cassandra.db.marshal.CounterColumnType<br /> Columns sorted by: org.apache.cassandra.db.marshal.BytesType<br /> Row cache size / save period in seconds: 0.0/0<br /> Key cache size / save period in seconds: 200000.0/14400<br /> Memtable thresholds: 0.0703125/1440/15 (millions of ops/minutes/MB)<br /> GC grace seconds: 864000<br /> Compaction min/max thresholds: 4/32<br /> Read repair chance: 1.0<br /> Replicate on write: false<br /> Built indexes: []</p> <p>Pig script:<br /> views = LOAD 'cassandra://SiteStats/views' USING CassandraStorage() AS (name, columns: bag {T: tuple(cname, cnt)});</p> <p>dump views; </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-515 Thu, 15 Sep 2011 03:40:23 +0000 cathy@datastax.com 515@http://www.datastax.com/support-forums/ <p>We have confirmed that Brisk is currently only compatible with Cassandra 0.8.3 and soon to be released 0.8.6. </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-509 Wed, 14 Sep 2011 18:10:57 +0000 cathy@datastax.com 509@http://www.datastax.com/support-forums/ <p>Can you try to use the IP address of the machines instead of localhost?<br /> I am trying to chase down some host resolution bugs when I run brisk with 0.8.5 and 1.0 but it seems if that each cluster I work with needs a slightly different specification: my mac works with localhost, my debian cluster requires hostname (not localhost or IP address). I'll run some tests today and see if it helps. </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-507 Wed, 14 Sep 2011 17:25:56 +0000 anthony.ikeda 507@http://www.datastax.com/support-forums/ <p>Okay, that didn't help at all. I'm guessing there are more configuration settings required than just that - I get the same result:</p> <p># Address to bind to and tell other Cassandra nodes to connect to. You<br /> # _must_ change this if you want multiple nodes to be able to<br /> # communicate!<br /> #<br /> # Leaving it blank leaves it up to InetAddress.getLocalHost(). This<br /> # will always do the Right Thing *if* the node is properly configured<br /> # (hostname, name resolution, etc), and the Right Thing is to use the<br /> # address associated with the hostname (it might not be).<br /> #<br /> # Setting this to 0.0.0.0 is always wrong.<br /> listen_address: localhost</p> <p># The address to bind the Thrift RPC service to -- clients connect<br /> # here. Unlike ListenAddress above, you *can* specify 0.0.0.0 here if<br /> # you want Thrift to listen on all interfaces.<br /> #<br /> # Leaving this blank has the same effect it does for ListenAddress,<br /> # (i.e. it will be based on the configured hostname of the node).<br /> # Brisk nodes should leave this as 0.0.0.0<br /> # rpc_address: 0.0.0.0<br /> rpc_address: localhost</p> <p>hive&gt; create external table Registry(registry_id string, external_id string, name string)<br /> &gt; stored by 'org.apache.hadoop.hive.cassandra.CassandraStorageHandler'<br /> &gt; with serdeproperties ("cassandra.columns.mapping" = "c-externalId,c-name")<br /> &gt; tblproperties ("cassandra.range.size" = "100",<br /> &gt; "cassandra.ks.name" = "RegistryFoundation","cassandra.slice.predicate.size" = "100" );<br /> OK<br /> Time taken: 0.092 seconds<br /> hive&gt; select * from Registry;<br /> OK<br /> Failed with exception java.io.IOException:java.io.IOException: Could not get input splits<br /> Time taken: 0.045 seconds<br /> hive&gt; </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-506 Wed, 14 Sep 2011 05:36:50 +0000 cathy@datastax.com 506@http://www.datastax.com/support-forums/ <p>Disregard the comment in the brisk cassandra.yaml file, and set rpc_address from '0.0.0.0' to the same value used for listen_address. I believe that should fix you. </p> <p>I encountered other issues running terasort which required that /etc/hosts was configured on all nodes, and once that was in place I needed to specify both listen_address and rpc_address to <code>hostname</code>. I am not sure if this last step will be required for you but thought that I would mention it. </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-503 Wed, 14 Sep 2011 00:16:36 +0000 anthony.ikeda 503@http://www.datastax.com/support-forums/ <p>Any progress on running Brisk with 0.8.5? I tried replacing the jars and although brisk cassandra -t works, when I try and query with hive I get:</p> <p>hive&gt; select * from Registry;<br /> OK<br /> Failed with exception java.io.IOException:java.io.IOException: Could not get input splits<br /> Time taken: 0.133 seconds </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-449 Thu, 18 Aug 2011 15:49:08 +0000 t0mas 449@http://www.datastax.com/support-forums/ <p>The update unfortunately causes issues, because of the changes in <a href="https://issues.apache.org/jira/browse/CASSANDRA-1777">CASSANDRA-1777</a>. Those changes caused a new problem where Cassandra accidentally adds a "/" character to the returned address, this is fixed in <a href="https://issues.apache.org/jira/browse/CASSANDRA-3044">CASSANDRA-3044</a> (for 0.8.5).</p> <p>The combination however still doesn't work, because when the node has its rpc_address set to "0.0.0.0" (required for Brisk to allow access from localhost) then it also returns "0.0.0.0" in TokenRange.endpoints which Brisk then tries to connect to during setup of the job, but connecting to "0.0.0.0" obviously doesn't work. </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-438 Mon, 15 Aug 2011 11:40:30 +0000 t0mas 438@http://www.datastax.com/support-forums/ <p>Thanks, I'll do so in our test environment and report how it worked out. Also a quick suggestion for the forum: You should add the "email me when a reply is received" option so people know when something is answered :-) </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-415 Tue, 09 Aug 2011 18:17:39 +0000 joaquin 415@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>I just spoke with our Brisk team and you should be fine with just replacing the jar file. If you were to be rebuilding it from source, then changing the dependency version should be all that is needed as well. At this point, the additional Brisk specific patches on top of Cassandra 0.8.1 are already apart of Cassandra core.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/building-brisk-from-source-to-update-cassandra-to-082#post-409 Mon, 08 Aug 2011 16:09:43 +0000 t0mas 409@http://www.datastax.com/support-forums/ <p>I have a few problems with Brisk-1.0-beta2 because it uses Cassandra 0.8.1 which has some bugs. These bugs are fixed in the 0.8.2 release of Cassandra so I'm looking for a way to "upgrade" my Brisk setup to the new Cassandra.</p> <p>The issue that's currently bothering me the most is CASSANDRA-2846: Changing replication_factor does not work.</p> <p>I looked into the source archive and found out that all files needed for creating a Debian package are in there. What would be the steps of upgrading the Cassandra version? Is there an overview of all Brisk specific patches that would need to be re-applied? Or could I just change the dependency version in the build-properties? </p>