Wide rows/composite keys clarification needed
Please correct me if I'm not describing this correctly. But if I am collecting sensor data and have a table defined as follows: create table sensor_data ( sensor_id int, time_stamp int, // time to the hour granularity voltage float, amp float, PRIMARY KEY (sensor_id, time_stamp) )); The partitioning value is the sensor_id and the rest of the PK components become part of the column name for the additional fields, in this case voltage and amp. What goes into determining what additional data is inserted into this row? The first time an insert takes place there will be one entry for all of the fields. Is there anything besides the sensor_id that is used to determine that the subsequent insertions for that sensor will go into the same row as opposed to starting a new row? Base on something I read (but can't currently find again), I thought that as long as all of the elements of the PK remain the same (same sensor_id and still within the same hour as the first reading), that the next insertion would be tacked onto the end of the first row. Is this correct? For subsequent entries into the same row for additional voltage/amp readings, what are the names of the columns for these readings? My understanding is that the column name becomes a concatenation of the non-row key field names plus the data field names.So if the first go-around you have : and :, what do the subsequent column names become? Thanks. Les
Re: Opscenter 3.2.2 (?) jmx auth issues
Hi Nick, thanks for getting back. Much appreciated. Cheers, Sven On Sat, Oct 19, 2013 at 3:58 AM, Nick Bailey wrote: > Sven, > > I've verified there is an issue with jmx authentication in the 3.2.2 > release. Thanks for the bug report! Sorry it's giving you issues. The bug > should be fixed in the next release of OpsCenter. > > Nick > > > On Wed, Oct 16, 2013 at 8:07 PM, Sven Stark wrote: > >> Hi guys, >> >> we have secured C* jmx with username/pw. We upgraded our Opscenter from >> 3.0.2 to 3.2.2 last week and noticed that the agents could not connect >> anymore >> >> ERROR [jmx-metrics-4] 2013-10-17 00:45:54,437 Error getting general >> metrics >> java.lang.SecurityException: Authentication failed! Credentials required >> at >> com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticationFailure(JMXPluggableAuthenticator.java:193) >> at >> com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticate(JMXPluggableAuthenticator.java:145) >> >> even though the credentials were correctly in >> /etc/opscenter/clusters/foo-cluster.conf >> >> [jmx] >> username = secret >> password = verysecret >> port = 20001 >> >> Checks with other jmx based tools (nodetool, jmxtrans) confirm that the >> jmx setup is correct. >> >> Downgrading Opscenter to 3.0.2 immediately resolved the issue. Could >> anybody confirm whether that's a known bug? >> >> >> Cheers, >> Sven >> > >