RocksDB in Kafka stream reporting no space when there is space available










1















I have a Streams application with a GlobalKtable backed by RocksDB that’s failing. I was originally getting the error described in https://issues.apache.org/jira/browse/KAFKA-6327, so I upgraded RocksDB to v5.14.2, which now gives a more explicit error: org.rocksdb.RocksDBException: While open a file for appending: /kafka_streams/...snip.../000295.sst: No space left on device



The directory in which the RocksDB spills to disk (a file mount on RHEL) seems to have ample space (Size: 5.4G Used: 2.8G Available: 2.6G Use%: 52%). I'm assuming that it's actually trying to allocate more than the remaining 2.6G, but that seems unlikely; there isn't that much data in the topic.



I found details on configuring RocksDB away from the defaults at https://docs.confluent.io/current/streams/developer-guide/config-streams.html#rocksdb-config-setter, but I don't see anything obvious that could potentially resolve the issue.



I haven't found any bug reports related to an issue like this, and I'm at a loss for troubleshooting next steps.




Edited to add:
I just ran the streams application on my local development machine against the same Kafka environment having the problem above. While the state stores were being loaded, the state store directory drifted up to a high of 3.1G and then settled at around 2.1G. It never got close to the 5G available on our development server. I haven't gotten any closer to finding an answer.










share|improve this question




























    1















    I have a Streams application with a GlobalKtable backed by RocksDB that’s failing. I was originally getting the error described in https://issues.apache.org/jira/browse/KAFKA-6327, so I upgraded RocksDB to v5.14.2, which now gives a more explicit error: org.rocksdb.RocksDBException: While open a file for appending: /kafka_streams/...snip.../000295.sst: No space left on device



    The directory in which the RocksDB spills to disk (a file mount on RHEL) seems to have ample space (Size: 5.4G Used: 2.8G Available: 2.6G Use%: 52%). I'm assuming that it's actually trying to allocate more than the remaining 2.6G, but that seems unlikely; there isn't that much data in the topic.



    I found details on configuring RocksDB away from the defaults at https://docs.confluent.io/current/streams/developer-guide/config-streams.html#rocksdb-config-setter, but I don't see anything obvious that could potentially resolve the issue.



    I haven't found any bug reports related to an issue like this, and I'm at a loss for troubleshooting next steps.




    Edited to add:
    I just ran the streams application on my local development machine against the same Kafka environment having the problem above. While the state stores were being loaded, the state store directory drifted up to a high of 3.1G and then settled at around 2.1G. It never got close to the 5G available on our development server. I haven't gotten any closer to finding an answer.










    share|improve this question


























      1












      1








      1








      I have a Streams application with a GlobalKtable backed by RocksDB that’s failing. I was originally getting the error described in https://issues.apache.org/jira/browse/KAFKA-6327, so I upgraded RocksDB to v5.14.2, which now gives a more explicit error: org.rocksdb.RocksDBException: While open a file for appending: /kafka_streams/...snip.../000295.sst: No space left on device



      The directory in which the RocksDB spills to disk (a file mount on RHEL) seems to have ample space (Size: 5.4G Used: 2.8G Available: 2.6G Use%: 52%). I'm assuming that it's actually trying to allocate more than the remaining 2.6G, but that seems unlikely; there isn't that much data in the topic.



      I found details on configuring RocksDB away from the defaults at https://docs.confluent.io/current/streams/developer-guide/config-streams.html#rocksdb-config-setter, but I don't see anything obvious that could potentially resolve the issue.



      I haven't found any bug reports related to an issue like this, and I'm at a loss for troubleshooting next steps.




      Edited to add:
      I just ran the streams application on my local development machine against the same Kafka environment having the problem above. While the state stores were being loaded, the state store directory drifted up to a high of 3.1G and then settled at around 2.1G. It never got close to the 5G available on our development server. I haven't gotten any closer to finding an answer.










      share|improve this question
















      I have a Streams application with a GlobalKtable backed by RocksDB that’s failing. I was originally getting the error described in https://issues.apache.org/jira/browse/KAFKA-6327, so I upgraded RocksDB to v5.14.2, which now gives a more explicit error: org.rocksdb.RocksDBException: While open a file for appending: /kafka_streams/...snip.../000295.sst: No space left on device



      The directory in which the RocksDB spills to disk (a file mount on RHEL) seems to have ample space (Size: 5.4G Used: 2.8G Available: 2.6G Use%: 52%). I'm assuming that it's actually trying to allocate more than the remaining 2.6G, but that seems unlikely; there isn't that much data in the topic.



      I found details on configuring RocksDB away from the defaults at https://docs.confluent.io/current/streams/developer-guide/config-streams.html#rocksdb-config-setter, but I don't see anything obvious that could potentially resolve the issue.



      I haven't found any bug reports related to an issue like this, and I'm at a loss for troubleshooting next steps.




      Edited to add:
      I just ran the streams application on my local development machine against the same Kafka environment having the problem above. While the state stores were being loaded, the state store directory drifted up to a high of 3.1G and then settled at around 2.1G. It never got close to the 5G available on our development server. I haven't gotten any closer to finding an answer.







      apache-kafka apache-kafka-streams rocksdb






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 17 '18 at 6:46







      Ickster

















      asked Nov 15 '18 at 20:13









      IcksterIckster

      1,33441736




      1,33441736






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I never found an answer to why the disk usage in the deployed environment was behaving this way, but I eventually got more space allocated out of desperation; as the stream was processing, it consumed as much as 14GB of space before settling down around 3-4GB. I assume the disk space error was because RocksDB was trying to allocate space, not that it had written to it.



          I've added a 'rule of thumb' that I should allocate 4x the disk space I expect for streaming applications.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53327225%2frocksdb-in-kafka-stream-reporting-no-space-when-there-is-space-available%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I never found an answer to why the disk usage in the deployed environment was behaving this way, but I eventually got more space allocated out of desperation; as the stream was processing, it consumed as much as 14GB of space before settling down around 3-4GB. I assume the disk space error was because RocksDB was trying to allocate space, not that it had written to it.



            I've added a 'rule of thumb' that I should allocate 4x the disk space I expect for streaming applications.






            share|improve this answer



























              0














              I never found an answer to why the disk usage in the deployed environment was behaving this way, but I eventually got more space allocated out of desperation; as the stream was processing, it consumed as much as 14GB of space before settling down around 3-4GB. I assume the disk space error was because RocksDB was trying to allocate space, not that it had written to it.



              I've added a 'rule of thumb' that I should allocate 4x the disk space I expect for streaming applications.






              share|improve this answer

























                0












                0








                0







                I never found an answer to why the disk usage in the deployed environment was behaving this way, but I eventually got more space allocated out of desperation; as the stream was processing, it consumed as much as 14GB of space before settling down around 3-4GB. I assume the disk space error was because RocksDB was trying to allocate space, not that it had written to it.



                I've added a 'rule of thumb' that I should allocate 4x the disk space I expect for streaming applications.






                share|improve this answer













                I never found an answer to why the disk usage in the deployed environment was behaving this way, but I eventually got more space allocated out of desperation; as the stream was processing, it consumed as much as 14GB of space before settling down around 3-4GB. I assume the disk space error was because RocksDB was trying to allocate space, not that it had written to it.



                I've added a 'rule of thumb' that I should allocate 4x the disk space I expect for streaming applications.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 25 at 19:42









                IcksterIckster

                1,33441736




                1,33441736





























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53327225%2frocksdb-in-kafka-stream-reporting-no-space-when-there-is-space-available%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    Barbados

                    How to read a connectionString WITH PROVIDER in .NET Core?

                    Node.js Script on GitHub Pages or Amazon S3