You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2010/08/15 22:12:17 UTC
[jira] Created: (CASSANDRA-1394) Blank listen_address/rpc_address
no longer binds based on hostname
Blank listen_address/rpc_address no longer binds based on hostname
------------------------------------------------------------------
Key: CASSANDRA-1394
URL: https://issues.apache.org/jira/browse/CASSANDRA-1394
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Brandon Williams
Assignee: Jon Hermes
With the switch to yamlbeans, if I make listen_address or rpc_address blank, they bind to localhost. Instead, they should bind to whatever hostname and /etc/hosts point at. This makes it much easier to use a unified config across a cluster. Also, yamlbeans doesn't respect the 'null' keyword, which should be the same as a blank value, but is instead treated as a literal string. This makes programmatic generation of the config file difficult.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1394) Blank listen_address/rpc_address
no longer binds based on hostname
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899390#action_12899390 ]
Hudson commented on CASSANDRA-1394:
-----------------------------------
Integrated in Cassandra #516 (See [https://hudson.apache.org/hudson/job/Cassandra/516/])
revert switch to yamlbeans. patch by jbellis; reviewed by Jon Hermes for CASSANDRA-1394
> Blank listen_address/rpc_address no longer binds based on hostname
> ------------------------------------------------------------------
>
> Key: CASSANDRA-1394
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1394
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 2
> Reporter: Brandon Williams
> Fix For: 0.7 beta 2
>
>
> With the switch to yamlbeans, if I make listen_address or rpc_address blank, they bind to localhost. Instead, they should bind to whatever hostname and /etc/hosts point at. This makes it much easier to use a unified config across a cluster. Also, yamlbeans doesn't respect the 'null' keyword, which should be the same as a blank value, but is instead treated as a literal string. This makes programmatic generation of the config file difficult.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-1394) Blank listen_address/rpc_address
no longer binds based on hostname
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-1394.
---------------------------------------
Assignee: (was: Jon Hermes)
Resolution: Fixed
reverted the yamlbeans switch.
> Blank listen_address/rpc_address no longer binds based on hostname
> ------------------------------------------------------------------
>
> Key: CASSANDRA-1394
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1394
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 2
> Reporter: Brandon Williams
> Fix For: 0.7 beta 2
>
>
> With the switch to yamlbeans, if I make listen_address or rpc_address blank, they bind to localhost. Instead, they should bind to whatever hostname and /etc/hosts point at. This makes it much easier to use a unified config across a cluster. Also, yamlbeans doesn't respect the 'null' keyword, which should be the same as a blank value, but is instead treated as a literal string. This makes programmatic generation of the config file difficult.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1394) Blank listen_address/rpc_address
no longer binds based on hostname
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1394:
--------------------------------------
Fix Version/s: 0.7 beta 2
Affects Version/s: 0.7 beta 2
(was: 0.7.0)
Component/s: Core
> Blank listen_address/rpc_address no longer binds based on hostname
> ------------------------------------------------------------------
>
> Key: CASSANDRA-1394
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1394
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 2
> Reporter: Brandon Williams
> Assignee: Jon Hermes
> Fix For: 0.7 beta 2
>
>
> With the switch to yamlbeans, if I make listen_address or rpc_address blank, they bind to localhost. Instead, they should bind to whatever hostname and /etc/hosts point at. This makes it much easier to use a unified config across a cluster. Also, yamlbeans doesn't respect the 'null' keyword, which should be the same as a blank value, but is instead treated as a literal string. This makes programmatic generation of the config file difficult.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.