Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4443

Cassandra SE: ERROR 1928 (HY000): Internal error: 'Thrift exception: Called write on non-open socket'

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0.1
    • Fix Version/s: 10.0.3
    • Component/s: None
    • Labels:
    • Environment:
      ubuntu 12.04 x64, M* 10.0.1

      Description

      to reproduce:
      create tbl (...) engine=cassandra ...
      use tbl;
      select smth from tbl;

      /restart cassandra/

      try to repeat last query:
      ERROR 1928 (HY000): Internal error: 'Thrift exception: write() send(): Broken pipe'
      ERROR 1928 (HY000): Internal error: 'Thrift exception: Called write on non-open socket'

      restart mysql service fixes problem.

      socket leak?
      and seems affected 10.0.2 too (at least looking in sources).

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            Does FLUSH TABLES help, by any chance?

            Show
            elenst Elena Stepanova added a comment - Does FLUSH TABLES help, by any chance?
            Hide
            karpa13a Mihail Karp added a comment -

            yep
            flush tables do same think as restart daemon

            Show
            karpa13a Mihail Karp added a comment - yep flush tables do same think as restart daemon
            Hide
            elenst Elena Stepanova added a comment -

            It might be reasonable then, but I'll forward it to Sergei to confirm (or to see if anything can/should be done about it).

            Show
            elenst Elena Stepanova added a comment - It might be reasonable then, but I'll forward it to Sergei to confirm (or to see if anything can/should be done about it).
            Hide
            psergey Sergei Petrunia added a comment -

            Fixed. Cassandra SE had a feature that would retry failed calls, but it only handled Cassandra's errors errors. Now, it handles network disconnects, also.

            Show
            psergey Sergei Petrunia added a comment - Fixed. Cassandra SE had a feature that would retry failed calls, but it only handled Cassandra's errors errors. Now, it handles network disconnects, also.

              People

              • Assignee:
                psergey Sergei Petrunia
                Reporter:
                karpa13a Mihail Karp
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h