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 (Created) (JIRA)" <ji...@apache.org> on 2012/03/20 05:31:45 UTC

[jira] [Created] (CASSANDRA-4064) cfstats should include the cfId

cfstats should include the cfId
-------------------------------

                 Key: CASSANDRA-4064
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4064
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Brandon Williams
            Assignee: Brandon Williams
             Fix For: 1.0.9


Specifically, when troubleshooting the dreaded "UnserializableColumnFamilyException: Couldn't find cfId=1001" type of error (and the schema is in agreement), it would be really useful to easily see the cfIds so you where the problem is (or is not)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-4064) cfstats should include the cfId

Posted by "Brandon Williams (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-4064:
----------------------------------------

    Description: Specifically, when troubleshooting the dreaded "UnserializableColumnFamilyException: Couldn't find cfId=1001" type of error (and the schema is in agreement), it would be really useful to easily see the cfIds so you know where the problem is (or is not)  (was: Specifically, when troubleshooting the dreaded "UnserializableColumnFamilyException: Couldn't find cfId=1001" type of error (and the schema is in agreement), it would be really useful to easily see the cfIds so you where the problem is (or is not))
    
> cfstats should include the cfId
> -------------------------------
>
>                 Key: CASSANDRA-4064
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4064
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.0.9
>
>
> Specifically, when troubleshooting the dreaded "UnserializableColumnFamilyException: Couldn't find cfId=1001" type of error (and the schema is in agreement), it would be really useful to easily see the cfIds so you know where the problem is (or is not)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-4064) cfstats should include the cfId

Posted by "Brandon Williams (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams updated CASSANDRA-4064:
----------------------------------------

    Priority: Minor  (was: Major)

This turned out to be CASSANDRA-3975, but still it could be handy if we have bugs here in the future.
                
> cfstats should include the cfId
> -------------------------------
>
>                 Key: CASSANDRA-4064
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4064
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 1.0.9
>
>
> Specifically, when troubleshooting the dreaded "UnserializableColumnFamilyException: Couldn't find cfId=1001" type of error (and the schema is in agreement), it would be really useful to easily see the cfIds so you know where the problem is (or is not)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CASSANDRA-4064) cfstats should include the cfId

Posted by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-4064.
---------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.0.10)
         Assignee:     (was: Brandon Williams)

Wontfixing this since 1.1 should be out soon and hopefully make UCFE obsolete.
                
> cfstats should include the cfId
> -------------------------------
>
>                 Key: CASSANDRA-4064
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4064
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brandon Williams
>            Priority: Minor
>
> Specifically, when troubleshooting the dreaded "UnserializableColumnFamilyException: Couldn't find cfId=1001" type of error (and the schema is in agreement), it would be really useful to easily see the cfIds so you know where the problem is (or is not)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira