opscenter

The following best practice checks fail when Cassandra's PasswordAuthenticator is enabled: Search nodes enabled with bad autocommit Search nodes enabled with query result cache Search nodes with bad filter cache My values are in compliance with the recommended values; and I have confirmed that the checks indeed pass when I disable authentication in Cassandra. What's weird is that there are 6 checks under the "Solr Advisor" category of the Best Practice Service and only these 3 are failing when authentication is enabled. Is this a known bug in Opscenter? I'm using v5.0.1 but I've seen this

I'm running Datastax Enterprise in a cluster consisting of 3 nodes. They are all running under the same hardware: 2 Core Intel Xeon 2.2 Ghz, 7 GB RAM, 4 TB Raid-0 This should be enough for running a cluster with a light load, storing less than 1 GB of data. Most of the time, everything is just fine but it appears that sometimes the running tasks related to the Repair Service in OpsCenter sometimes get stuck; this causes an instability in that node and an increase in load. However, if the node is restarted, the stuck tasks don't show up and the load is at normal levels again. Because of the

I believe I have found a bug with the logic of how a prepared statement is cached in the StatementFactory in the Cassandra csharp driver (version 2.7.3). Here is the use case. Guid key = Guid.NewGuid(); // your key ISession session_foo = new Session("foo"); //This is pseudo code ISession session_bar = new Session("bar"); var foo_mapper = new Mapper(session_foo); //table foo_bar var bar_mapper = new Mapper(session_bar); //table foo_bar await Task.WhenAll( foo_mapper.DeleteAsync<Foo>("WHERE id = ?", key), bar_mapper.DeleteAsync<Bar>("WHERE id = ?", key)); We have found that after running this

I upgraded OpsCenter from 5.1.3 to 5.2.0 (and then to 5.2.1). I had a scheduled backup to local server and an S3 location configured before the upgrade, which worked fine with OpsCenter 5.1.3. I made to no changes to the scheduled backup during or after the upgrade. The day after the upgrade, the S3 backup failed. In opscenterd.log, I see these errors: 2015-09-28 17:00:00+0000 [local] INFO: Instructing agents to start backups at Mon, 28 Sep 2015 17:00:00 +0000 2015-09-28 17:00:00+0000 [local] INFO: Scheduled job 458459d6-d038-41b4-9094-7d450e4bac6f finished 2015-09-28 17:00:00+0000 [local]

Update 2 There was a bug in Opscenter not matching dsc22 configuration with cassandra community version, this solved one problem. Update After reading the opscenter log again I think there actually something wrong with the 4 authentication fields or some ssh configuration, but I still don't know what exactly should be done, The field says "Local node credentials (sudo) private key (optional) the scenario is as following: I installed 4 nodes with vagrant and ansible where each has dsc22,opscenter (redundant I know),datastax-agent,cassandra-tool, oracle java 8 configuration below nodetool status