You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/05/02 18:50:17 UTC

[jira] [Updated] (CASSANDRA-5150) sstable2json doesn't check SIGPIPE

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

Jonathan Ellis updated CASSANDRA-5150:
--------------------------------------

             Reviewer: jbellis
    Affects Version/s:     (was: 2.0)
        Fix Version/s: 2.0
             Assignee: Pawel Mirski

LGTM; committed.  Thanks, Pawel!
                
> sstable2json doesn't check SIGPIPE
> ----------------------------------
>
>                 Key: CASSANDRA-5150
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5150
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>            Reporter: Will Oberman
>            Assignee: Pawel Mirski
>            Priority: Minor
>              Labels: lhf
>             Fix For: 2.0
>
>         Attachments: trunk-5150.txt
>
>
> I believe this explains the issue better than I can: http://stackoverflow.com/questions/11695500/how-do-i-get-java-to-exit-when-piped-to-head.
> Basically, I expected that if I did: "sstable2json SSTABLE | other-process", and other-process had issues and/or died then the sstable2json process would die.  It doesn't.  
> My workaround is using mkfifo FILE, and having sstable2json write to FILE, other-process read from FILE, and a 3rd overall process make sure the other two processes are working.  But, it would be _much_ simplier if sstable2json failed on SIGPIPE.
> I looks like the fix is to periodically check System.out.checkError() in the Java.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira