Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14781

Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough

    XMLWordPrintableJSON

Details

    Description

      When hitting https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L256-L257, the log message produced does not help the operator track down what data is being written. At a minimum the keyspace and cfIds involved would be useful (and are available) – more detail might not be reasonable to include. 

      Attachments

        1. CASSANDRA-14781.patch
          1 kB
          Tom Petracca
        2. CASSANDRA-14781_3.11.patch
          3 kB
          Leon Zaruvinsky
        3. CASSANDRA-14781_3.0.patch
          2 kB
          Tom Petracca

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-14782 Make DatabaseDescriptor.getNativeTransportMaxFrameSize() a hotprop

          • Normal -
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. CASSANDRA-12231 Make large mutations easier to find

          • Low -
          • Open
          relates to

          Task - A task that needs to be done. CASSANDRA-15741 Mutation size exceeds max limit - clients get timeout?

          • Normal -
          • Triage Needed

          Activity

            People

              n.v.harikrishna n.v.harikrishna
              jwest Jordan West
              n.v.harikrishna
              Chris Lohfink, Jordan West
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: