[jira] [Resolved] (USERGRID-51) the result from the Setup call (to setup DB) should not say OK when it failed to create KS (or other critical failure)

["Michael Russo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/USERGRID-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Russo resolved USERGRID-51.
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.0.1)
                   1.0.2

> the result from the Setup call (to setup DB) should not say OK when it failed to create KS (or other critical failure)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: USERGRID-51
>                 URL: https://issues.apache.org/jira/browse/USERGRID-51
>             Project: Usergrid
>          Issue Type: Bug
>          Components: Stack
>            Reporter: Rod Simpson
>             Fix For: 1.0.2
>
>
> **Need to verify that this is still an issue
> "When the /setup call is run and create UG keyspaces, they could fail (for various reason). 
> However, it seems in the result from the call, the status always says OK: 
> {panel} 
> [root@rut000ea lib]# curl -u superuser:supervisor 0:8080/system/database/setup 
> \{ 
> ""action"" : ""cassandra setup"", 
> ""status"" : ""ok"", 
> ""timestamp"" : 1383342928369, 
> ""duration"" : 65 
> \} 
> {panel} 
> Here is 1 way to reproduce this problem: in the usergrid properties, define to use NetworkTopologyStrategy AND replication_factor: 
> {panel} 
> cassandra.keyspace.strategy.options.replication_factor=3 
> cassandra.keyspace.strategy.options.us-east=3 
> cassandra.keyspace.strategy=org.apache.cassandra.locator.NetworkTopologyStrategy 
> {panel} 
> In C* 1.2, it becomes stricter on the options used (previously a warning). The above combination of the strategy options is invalid for NetworkTopologyStrategy, and will result in failure of creating the keyspace. 
> Hence the status result from the setup call should reflect it."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)