[jira] [Updated] (CASSANDRA-9678) help describe is missing the documentation for UDTs
[ https://issues.apache.org/jira/browse/CASSANDRA-9678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday updated CASSANDRA-9678: -- Summary: help describe is missing the documentation for UDTs (was: help describe is missing the documentation for UDFs) help describe is missing the documentation for UDTs --- Key: CASSANDRA-9678 URL: https://issues.apache.org/jira/browse/CASSANDRA-9678 Project: Cassandra Issue Type: Improvement Reporter: Peter Halliday Priority: Minor Labels: cqlsh Fix For: 2.1.x On 2.1 when you type help describe, the documentation for describe types is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-9678) help describe is missing the documentation for UDTs
[ https://issues.apache.org/jira/browse/CASSANDRA-9678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608665#comment-14608665 ] Peter Halliday commented on CASSANDRA-9678: --- UDTs, you are correct. Changed summary. help describe is missing the documentation for UDTs --- Key: CASSANDRA-9678 URL: https://issues.apache.org/jira/browse/CASSANDRA-9678 Project: Cassandra Issue Type: Improvement Reporter: Peter Halliday Priority: Minor Labels: cqlsh Fix For: 2.1.x On 2.1 when you type help describe, the documentation for describe types is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-9678) help describe is missing the documentation for UDFs
Peter Halliday created CASSANDRA-9678: - Summary: help describe is missing the documentation for UDFs Key: CASSANDRA-9678 URL: https://issues.apache.org/jira/browse/CASSANDRA-9678 Project: Cassandra Issue Type: Improvement Reporter: Peter Halliday Priority: Minor On 2.1 when you type help describe, the documentation for describe types is missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-8794) AntiEntropySessions doesn't show up until after a repair
Peter Halliday created CASSANDRA-8794: - Summary: AntiEntropySessions doesn't show up until after a repair Key: CASSANDRA-8794 URL: https://issues.apache.org/jira/browse/CASSANDRA-8794 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday The metric AntiEntropySessions for internal thread pools doesn't actually show up as an mbean until after a repair is run. This should actually be displayed before. This also, keeps any cluster that doesn't need repairing from displaying stats for AntiEntropySessions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CASSANDRA-8794) AntiEntropySessions doesn't show up until after a repair
[ https://issues.apache.org/jira/browse/CASSANDRA-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday updated CASSANDRA-8794: -- Description: The metric AntiEntropySessions for internal thread pools doesn't actually show up as an mbean until after a repair is run. This should actually be displayed before. This also, keeps any cluster that doesn't need repairing from displaying stats for AntiEntropySessions. The lack of the mbean's existence until after the repair will cause problem for various monitoring tools. (was: The metric AntiEntropySessions for internal thread pools doesn't actually show up as an mbean until after a repair is run. This should actually be displayed before. This also, keeps any cluster that doesn't need repairing from displaying stats for AntiEntropySessions.) AntiEntropySessions doesn't show up until after a repair Key: CASSANDRA-8794 URL: https://issues.apache.org/jira/browse/CASSANDRA-8794 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday The metric AntiEntropySessions for internal thread pools doesn't actually show up as an mbean until after a repair is run. This should actually be displayed before. This also, keeps any cluster that doesn't need repairing from displaying stats for AntiEntropySessions. The lack of the mbean's existence until after the repair will cause problem for various monitoring tools. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CASSANDRA-8348) allow takeColumnFamilySnapshot to take a list of ColumnFamilies
Peter Halliday created CASSANDRA-8348: - Summary: allow takeColumnFamilySnapshot to take a list of ColumnFamilies Key: CASSANDRA-8348 URL: https://issues.apache.org/jira/browse/CASSANDRA-8348 Project: Cassandra Issue Type: Improvement Reporter: Peter Halliday Priority: Minor Within StorageServiceMBean.java the function takeSnapshot allows for a list of keyspaces to snapshot. However, the function takeColumnFamilySnapshot only allows for a single ColumnFamily to snapshot. This should allow for multiple ColumnFamilies within the same Keyspace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status
[ https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837066#comment-13837066 ] Peter Halliday commented on CASSANDRA-6399: --- This actually seems to work with 2.0.2. debian init script removes PID despite the return status Key: CASSANDRA-6399 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway. This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status
[
https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837076#comment-13837076
]
Peter Halliday commented on CASSANDRA-6399:
---
I followed this: http://www.datastax.com/docs/1.1/install/install_deb, the
following fails. The one after that works.
{noformat}
automaton@ip-10-32-35-198:~/cassandra$ sudo apt-get install cassandra=2.0.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
cassandra
0 upgraded, 1 newly installed, 0 to remove and 93 not upgraded.
Need to get 14.1 MB of archives.
After this operation, 16.1 MB of additional disk space will be used.
Get:1 http://debian.datastax.com/community/ stable/main cassandra all 2.0.1
[14.1 MB]
Fetched 14.1 MB in 1s (8,983 kB/s)
Selecting previously unselected package cassandra.
(Reading database ... 49953 files and directories currently installed.)
Unpacking cassandra (from .../cassandra_2.0.1_all.deb) ...
Processing triggers for ureadahead ...
Setting up cassandra (2.0.1) ...
Installing new version of config file /etc/cassandra/cassandra.yaml ...
Installing new version of config file /etc/cassandra/cassandra-env.sh ...
Installing new version of config file /etc/init.d/cassandra ...
vm.max_map_count = 1048575
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
Processing triggers for python-support ...
automaton@ip-10-32-35-198:~/cassandra$ sudo service cassandra status
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
* could not access pidfile for Cassandra
{noformat}
Then when did the same with 2.0.2, it does start correctly.
{noformat}
automaton@ip-10-32-35-198:~$ sudo apt-get install cassandra=2.0.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
cassandra
0 upgraded, 1 newly installed, 0 to remove and 93 not upgraded.
Need to get 0 B/14.2 MB of archives.
After this operation, 16.1 MB of additional disk space will be used.
Selecting previously unselected package cassandra.
(Reading database ... 49953 files and directories currently installed.)
Unpacking cassandra (from .../cassandra_2.0.2_all.deb) ...
Processing triggers for ureadahead ...
Setting up cassandra (2.0.2) ...
Installing new version of config file /etc/cassandra/cassandra.yaml ...
Installing new version of config file /etc/cassandra/cassandra-env.sh ...
Installing new version of config file /etc/init.d/cassandra ...
vm.max_map_count = 1048575
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
Processing triggers for python-support ...
automaton@ip-10-32-35-198:~$ sudo service cassandra status
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
* Cassandra is running
{noformat}
I tried updating the definition file to add 2.0.2 to the drop down box for
installation, but that may not have been enough.
debian init script removes PID despite the return status
Key: CASSANDRA-6399
URL: https://issues.apache.org/jira/browse/CASSANDRA-6399
Project: Cassandra
Issue Type: Bug
Reporter: Peter Halliday
If there's an error in running service cassandra stop it can return a
non-successful code, but the do_stop() removes the PID file anyway. This
shows then via service cassandra status, that Cassandra is stopped, even
though it's still running in the process list.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Issue Comment Deleted] (CASSANDRA-6399) debian init script removes PID despite the return status
[
https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Halliday updated CASSANDRA-6399:
--
Comment: was deleted
(was: I followed this: http://www.datastax.com/docs/1.1/install/install_deb,
the following fails. The one after that works.
{noformat}
automaton@ip-10-32-35-198:~/cassandra$ sudo apt-get install cassandra=2.0.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
cassandra
0 upgraded, 1 newly installed, 0 to remove and 93 not upgraded.
Need to get 14.1 MB of archives.
After this operation, 16.1 MB of additional disk space will be used.
Get:1 http://debian.datastax.com/community/ stable/main cassandra all 2.0.1
[14.1 MB]
Fetched 14.1 MB in 1s (8,983 kB/s)
Selecting previously unselected package cassandra.
(Reading database ... 49953 files and directories currently installed.)
Unpacking cassandra (from .../cassandra_2.0.1_all.deb) ...
Processing triggers for ureadahead ...
Setting up cassandra (2.0.1) ...
Installing new version of config file /etc/cassandra/cassandra.yaml ...
Installing new version of config file /etc/cassandra/cassandra-env.sh ...
Installing new version of config file /etc/init.d/cassandra ...
vm.max_map_count = 1048575
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
Processing triggers for python-support ...
automaton@ip-10-32-35-198:~/cassandra$ sudo service cassandra status
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
* could not access pidfile for Cassandra
{noformat}
Then when did the same with 2.0.2, it does start correctly.
{noformat}
automaton@ip-10-32-35-198:~$ sudo apt-get install cassandra=2.0.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
cassandra
0 upgraded, 1 newly installed, 0 to remove and 93 not upgraded.
Need to get 0 B/14.2 MB of archives.
After this operation, 16.1 MB of additional disk space will be used.
Selecting previously unselected package cassandra.
(Reading database ... 49953 files and directories currently installed.)
Unpacking cassandra (from .../cassandra_2.0.2_all.deb) ...
Processing triggers for ureadahead ...
Setting up cassandra (2.0.2) ...
Installing new version of config file /etc/cassandra/cassandra.yaml ...
Installing new version of config file /etc/cassandra/cassandra-env.sh ...
Installing new version of config file /etc/init.d/cassandra ...
vm.max_map_count = 1048575
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
Processing triggers for python-support ...
automaton@ip-10-32-35-198:~$ sudo service cassandra status
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
* Cassandra is running
{noformat}
I tried updating the definition file to add 2.0.2 to the drop down box for
installation, but that may not have been enough.)
debian init script removes PID despite the return status
Key: CASSANDRA-6399
URL: https://issues.apache.org/jira/browse/CASSANDRA-6399
Project: Cassandra
Issue Type: Bug
Reporter: Peter Halliday
If there's an error in running service cassandra stop it can return a
non-successful code, but the do_stop() removes the PID file anyway. This
shows then via service cassandra status, that Cassandra is stopped, even
though it's still running in the process list.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (CASSANDRA-6399) debian init script removes PID despite the return status
Peter Halliday created CASSANDRA-6399: - Summary: debian init script removes PID despite the return status Key: CASSANDRA-6399 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway. This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status
[ https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830348#comment-13830348 ] Peter Halliday commented on CASSANDRA-6399: --- Also, start-stop-daemon doesn't block until it's stopped. With the current command line. So it returns success as soon as the signal was sent. This could lead to situations if the signal was ignored for some reason that it was read as a success. I suggest adding the --retry flag, which can have a timeout added as well if desired. debian init script removes PID despite the return status Key: CASSANDRA-6399 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway. This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Issue Comment Deleted] (CASSANDRA-6399) debian init script removes PID despite the return status
[ https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday updated CASSANDRA-6399: -- Comment: was deleted (was: Also, start-stop-daemon doesn't block until it's stopped. With the current command line. So it returns success as soon as the signal was sent. This could lead to situations if the signal was ignored for some reason that it was read as a success. I suggest adding the --retry flag, which can have a timeout added as well if desired.) debian init script removes PID despite the return status Key: CASSANDRA-6399 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway. This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status
[
https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830382#comment-13830382
]
Peter Halliday commented on CASSANDRA-6399:
---
Also, on debian, there's no /var/run/cassandra directory created. So that
means the PID file doesn't get created
{noformat}
ubuntu@domU-12-31-39-02-85-9C:~$ ps aux|grep cassandra
ubuntu@domU-12-31-39-02-85-9C:~$ sudo service cassandra start
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
ubuntu@domU-12-31-39-02-85-9C:~$ sudo service cassandra status
xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M
-Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
* Cassandra is not running
ubuntu@domU-12-31-39-02-85-9C:~$
{noformat}
debian init script removes PID despite the return status
Key: CASSANDRA-6399
URL: https://issues.apache.org/jira/browse/CASSANDRA-6399
Project: Cassandra
Issue Type: Bug
Reporter: Peter Halliday
If there's an error in running service cassandra stop it can return a
non-successful code, but the do_stop() removes the PID file anyway. This
shows then via service cassandra status, that Cassandra is stopped, even
though it's still running in the process list.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status
[ https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13830435#comment-13830435 ] Peter Halliday commented on CASSANDRA-6399: --- 2.0.1 debian init script removes PID despite the return status Key: CASSANDRA-6399 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway. This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CASSANDRA-6286) Add JMX auth password file location info to cassandra-env.sh
Peter Halliday created CASSANDRA-6286: - Summary: Add JMX auth password file location info to cassandra-env.sh Key: CASSANDRA-6286 URL: https://issues.apache.org/jira/browse/CASSANDRA-6286 Project: Cassandra Issue Type: New Feature Reporter: Peter Halliday Priority: Trivial Attachments: 0001-Add-jmx-auth-file-location-comment-to-aid-in-setup.patch If you are running JMX authentication, and don't want to run cassandra as root, you need to ensure that JMX auth file is owned by cassandra user. This is best if, then the JMX auth file is setup not in the system location. To aid in this, would be helpful to have cassandra-env.sh have at least a commented out line that shows a suggestion for this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CASSANDRA-6286) Add JMX auth password file location info to cassandra-env.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday updated CASSANDRA-6286: -- Attachment: 0001-Add-jmx-auth-file-location-comment-to-aid-in-setup.patch Attach is a patch file against trunk accomplishing this. Add JMX auth password file location info to cassandra-env.sh Key: CASSANDRA-6286 URL: https://issues.apache.org/jira/browse/CASSANDRA-6286 Project: Cassandra Issue Type: New Feature Reporter: Peter Halliday Priority: Trivial Attachments: 0001-Add-jmx-auth-file-location-comment-to-aid-in-setup.patch If you are running JMX authentication, and don't want to run cassandra as root, you need to ensure that JMX auth file is owned by cassandra user. This is best if, then the JMX auth file is setup not in the system location. To aid in this, would be helpful to have cassandra-env.sh have at least a commented out line that shows a suggestion for this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-6286) Add JMX auth password file location info to cassandra-env.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811698#comment-13811698 ] Peter Halliday commented on CASSANDRA-6286: --- Created with git format-patch. would you rather it with something else? Add JMX auth password file location info to cassandra-env.sh Key: CASSANDRA-6286 URL: https://issues.apache.org/jira/browse/CASSANDRA-6286 Project: Cassandra Issue Type: New Feature Components: Config Reporter: Peter Halliday Assignee: Peter Halliday Priority: Trivial Fix For: 1.2.12 Attachments: 0001-Add-jmx-auth-file-location-comment-to-aid-in-setup.patch If you are running JMX authentication, and don't want to run cassandra as root, you need to ensure that JMX auth file is owned by cassandra user. This is best if, then the JMX auth file is setup not in the system location. To aid in this, would be helpful to have cassandra-env.sh have at least a commented out line that shows a suggestion for this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CASSANDRA-6286) Add JMX auth password file location info to cassandra-env.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811710#comment-13811710 ] Peter Halliday commented on CASSANDRA-6286: --- It's against truck. Should I make it against 1.2 branch instead? Add JMX auth password file location info to cassandra-env.sh Key: CASSANDRA-6286 URL: https://issues.apache.org/jira/browse/CASSANDRA-6286 Project: Cassandra Issue Type: New Feature Components: Config Reporter: Peter Halliday Assignee: Peter Halliday Priority: Trivial Fix For: 1.2.12 Attachments: 0001-Add-jmx-auth-file-location-comment-to-aid-in-setup.patch If you are running JMX authentication, and don't want to run cassandra as root, you need to ensure that JMX auth file is owned by cassandra user. This is best if, then the JMX auth file is setup not in the system location. To aid in this, would be helpful to have cassandra-env.sh have at least a commented out line that shows a suggestion for this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (CASSANDRA-6286) Add JMX auth password file location info to cassandra-env.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811710#comment-13811710 ] Peter Halliday edited comment on CASSANDRA-6286 at 11/1/13 10:36 PM: - It's against trunk. Should I make it against 1.2 branch instead? was (Author: hoangelos): It's against truck. Should I make it against 1.2 branch instead? Add JMX auth password file location info to cassandra-env.sh Key: CASSANDRA-6286 URL: https://issues.apache.org/jira/browse/CASSANDRA-6286 Project: Cassandra Issue Type: New Feature Components: Config Reporter: Peter Halliday Assignee: Peter Halliday Priority: Trivial Fix For: 1.2.12 Attachments: 0001-Add-jmx-auth-file-location-comment-to-aid-in-setup.patch If you are running JMX authentication, and don't want to run cassandra as root, you need to ensure that JMX auth file is owned by cassandra user. This is best if, then the JMX auth file is setup not in the system location. To aid in this, would be helpful to have cassandra-env.sh have at least a commented out line that shows a suggestion for this. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CASSANDRA-6279) command-line tool shouldn't require password
Peter Halliday created CASSANDRA-6279: - Summary: command-line tool shouldn't require password Key: CASSANDRA-6279 URL: https://issues.apache.org/jira/browse/CASSANDRA-6279 Project: Cassandra Issue Type: Bug Reporter: Peter Halliday Priority: Minor If you use nodetool and cassandra-cli, and have Thrift authentication, then you are required to pass in the password on the command-line. This is a potential security issue. For those that choose to do so, that's fine. However, ideally, there would be a method of not doing that, which would prompt you to enter a password. Understanding that no method is complete secure, this would be certainly more so. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] Commented: (CASSANDRA-786) RPM Packages
[ https://issues.apache.org/jira/browse/CASSANDRA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12890381#action_12890381 ] Peter Halliday commented on CASSANDRA-786: -- Riptano also has a Yum repository for RPMS of cassandra that will install them in a binary mode. You can access them at http://rpm.riptano.com/. Pick the OS and version you are using. Install riptano-release package and it will point to the repo for you to do a yum install cassandra. Then you have to copy the storage-conf.xml from /usr/local/cassandra to /etc/cassandra and edit as necessary. Also, cassandra.in.sh may need to be edited. RPM Packages Key: CASSANDRA-786 URL: https://issues.apache.org/jira/browse/CASSANDRA-786 Project: Cassandra Issue Type: Improvement Components: Contrib Reporter: Daniel Lundin Assignee: Peter Halliday Priority: Minor Attachments: 768-update-spec-for-trunk.diff, 786-adjust-jars.patch, cassandra.spec, cassandra.spec RPM packages (and debs of course) would be nice,especially now that cassandra is maturing and gaining more interest. Lowering the threshold for getting cassandra running and getting started is also important. I think the RabbitMQ project has an admirable Download and install experience, not to mention the rather cute 2 min guarantee. Definitely a good inspiration. I've been studying Cloudera's Hadoop packages, which are very nice, and really appreciate the separate packages for configuration. This allows easy deployment of node configuration to a cluster. I'll have a spec file for building RHEL5 / CentOS packages ready for review and attached here in a bit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-786) RPM Packages
[ https://issues.apache.org/jira/browse/CASSANDRA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday resolved CASSANDRA-786. -- Resolution: Fixed Long term, I'll be creating a document on a wiki somewhere where we can track progress for the RPMs for the dependencies. RPM Packages Key: CASSANDRA-786 URL: https://issues.apache.org/jira/browse/CASSANDRA-786 Project: Cassandra Issue Type: Improvement Components: Contrib Reporter: Daniel Lundin Assignee: Peter Halliday Priority: Minor Attachments: 768-update-spec-for-trunk.diff, 786-adjust-jars.patch, cassandra.spec, cassandra.spec RPM packages (and debs of course) would be nice,especially now that cassandra is maturing and gaining more interest. Lowering the threshold for getting cassandra running and getting started is also important. I think the RabbitMQ project has an admirable Download and install experience, not to mention the rather cute 2 min guarantee. Definitely a good inspiration. I've been studying Cloudera's Hadoop packages, which are very nice, and really appreciate the separate packages for configuration. This allows easy deployment of node configuration to a cluster. I'll have a spec file for building RHEL5 / CentOS packages ready for review and attached here in a bit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-786) RPM Packages
[ https://issues.apache.org/jira/browse/CASSANDRA-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday updated CASSANDRA-786: - Attachment: cassandra.spec This spec will not compile a Fedora compliant binary. However, it will work until the dependencies are all converted to RPM. The big issue is that RedHat/Fedora requires that all jars be installed into the java system path unless it's only app specific code. So, getting in those OS' will be harder. But until then this will provide a working RPM on 0.6.2 and above. RPM Packages Key: CASSANDRA-786 URL: https://issues.apache.org/jira/browse/CASSANDRA-786 Project: Cassandra Issue Type: Improvement Components: Contrib Reporter: Daniel Lundin Assignee: Peter Halliday Priority: Minor Attachments: 768-update-spec-for-trunk.diff, 786-adjust-jars.patch, cassandra.spec, cassandra.spec RPM packages (and debs of course) would be nice,especially now that cassandra is maturing and gaining more interest. Lowering the threshold for getting cassandra running and getting started is also important. I think the RabbitMQ project has an admirable Download and install experience, not to mention the rather cute 2 min guarantee. Definitely a good inspiration. I've been studying Cloudera's Hadoop packages, which are very nice, and really appreciate the separate packages for configuration. This allows easy deployment of node configuration to a cluster. I'll have a spec file for building RHEL5 / CentOS packages ready for review and attached here in a bit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CASSANDRA-1201) Red Hat files needed for packaging
Red Hat files needed for packaging -- Key: CASSANDRA-1201 URL: https://issues.apache.org/jira/browse/CASSANDRA-1201 Project: Cassandra Issue Type: New Feature Components: Contrib Reporter: Peter Halliday Priority: Minor The following files are needed for packaging an RPM. This is in line with the debian based things put in contrib. A spec file, an init script. I would prefer that this go in a redhat folder. And then fedora and RHEL can use it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1201) Red Hat files needed for packaging
[ https://issues.apache.org/jira/browse/CASSANDRA-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Halliday updated CASSANDRA-1201: -- Attachment: cassandra Uploading cassandra init file Red Hat files needed for packaging -- Key: CASSANDRA-1201 URL: https://issues.apache.org/jira/browse/CASSANDRA-1201 Project: Cassandra Issue Type: New Feature Components: Contrib Reporter: Peter Halliday Priority: Minor Attachments: cassandra The following files are needed for packaging an RPM. This is in line with the debian based things put in contrib. A spec file, an init script. I would prefer that this go in a redhat folder. And then fedora and RHEL can use it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1201) Red Hat files needed for packaging
[ https://issues.apache.org/jira/browse/CASSANDRA-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12880050#action_12880050 ] Peter Halliday commented on CASSANDRA-1201: --- I have one ready but before its done need an init script. Its a chicken or egg issue. This will allow for RPM but not acceptance into redhat per se. That will take longer, but will be putting a yum repo. Up tomorrow. Red Hat files needed for packaging -- Key: CASSANDRA-1201 URL: https://issues.apache.org/jira/browse/CASSANDRA-1201 Project: Cassandra Issue Type: New Feature Components: Contrib Reporter: Peter Halliday Priority: Minor Attachments: cassandra The following files are needed for packaging an RPM. This is in line with the debian based things put in contrib. A spec file, an init script. I would prefer that this go in a redhat folder. And then fedora and RHEL can use it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
