Installation Failure

I get the following error, every attempt to install, always on "Upsource Cluster Initialize Service". 

Windows Server 2008R2, 8 gig ram.

 

[2016-09-16 13:16:36,421] * Starting Upsource Cluster Initialize Service
[2016-09-16 13:17:15,044] upsource-cluster-init: [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
[2016-09-16 13:17:15,044] upsource-cluster-init: [Upsource Cluster Initialize Service Error] log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
[2016-09-16 13:17:15,045] upsource-cluster-init: [Upsource Cluster Initialize Service Error] [2016-09-16 13:17:05,574] WARN APP-WRAPPER] Proxy 1 datastax.driver.core.NettyUtil - Found Netty's native epoll transport, but not running on linux-based operating system. Using NIO instead.
[2016-09-16 13:17:15,045] upsource-cluster-init: [Upsource Cluster Initialize Service Error] [2016-09-16 13:17:14,895] ERROR oration 1.8.0_91-b14 atabase.datastax.WriteExecutor - InvalidQueryException while writing to cassandra, [SCHEMA]:
[2016-09-16 13:17:15,045] upsource-cluster-init: [Upsource Cluster Initialize Service Error] CREATE KEYSPACE zip WITH REPLICATION = { 'class' : 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '1' } AND DURABLE_WRITES = true;
[2016-09-16 13:17:15,045] upsource-cluster-init: [Upsource Cluster Initialize Service Error]
[2016-09-16 13:17:15,045] upsource-cluster-init: [Upsource Cluster Initialize Service Error] CREATE TABLE zip.libraryideaindex (
[2016-09-16 13:17:15,045] upsource-cluster-init: [Upsource Cluster Initialize Service Error] databaseid blob,
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] columnid blob,
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] value blob,
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] PRIMARY KEY (databaseid, columnid)
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] ) WITH COMPACT STORAGE
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND read_repair_chance = 0.0
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND dclocal_read_repair_chance = 0.1
[2016-09-16 13:17:15,046] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND gc_grace_seconds = 7200
[2016-09-16 13:17:15,049] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND bloom_filter_fp_chance = 0.1
[2016-09-16 13:17:15,049] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND caching = { 'keys' : 'ALL', 'rows_per_partition' : 'NONE' }
[2016-09-16 13:17:15,050] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND comment = ''
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND compaction = { 'class' : 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy' }
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND compression = { 'sstable_compression' : 'org.apache.cassandra.io.compress.LZ4Compressor' }
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND default_time_to_live = 0
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND speculative_retry = '99.0PERCENTILE'
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND min_index_interval = 128
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error] AND max_index_interval = 2048;
[2016-09-16 13:17:15,052] upsource-cluster-init: [Upsource Cluster Initialize Service Error]

And so on, with the rest of the DB create statements.

 

1 comment

Hi Troy,

Could you please open a support ticket with full Upsource logs attached?

Seems to be an issue with a DB, but from the given output it's not really obvious what happened.

0

Please sign in to leave a comment.