Running Hadoop 2.8.0 on Windows 10, YarnRuntimeException Permissions incorrectly set, should be rwxr-xr-x,...












0















I recently followed article https://www.quora.com/How-do-I-install-Hadoop-2-8-2-on-Windows-10-for-practice, and tried to run Hadoop on my Windows 10 machine (i7, 16GB RAM). It started correctly - no issues. But when I installed Docker, which inturn enabled Hyper-V, I started to get following failure while starting NodeManager



18/12/19 21:29:31 INFO ipc.Server: IPC Server listener on 8040: starting
18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
18/12/19 21:29:31 INFO localizer.ResourceLocalizationService: Attempting to initialize /tmp/hadoop-username/nm-local-dir
18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Failed to setup local dir /tmp/hadoop-username/nm-local-dir, which was marked as good.
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
...


Following services start without any issues




  • ResourceManager

  • datanode

  • namenode










share|improve this question



























    0















    I recently followed article https://www.quora.com/How-do-I-install-Hadoop-2-8-2-on-Windows-10-for-practice, and tried to run Hadoop on my Windows 10 machine (i7, 16GB RAM). It started correctly - no issues. But when I installed Docker, which inturn enabled Hyper-V, I started to get following failure while starting NodeManager



    18/12/19 21:29:31 INFO ipc.Server: IPC Server listener on 8040: starting
    18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
    18/12/19 21:29:31 INFO localizer.ResourceLocalizationService: Attempting to initialize /tmp/hadoop-username/nm-local-dir
    18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
    18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Failed to setup local dir /tmp/hadoop-username/nm-local-dir, which was marked as good.
    org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
    ...


    Following services start without any issues




    • ResourceManager

    • datanode

    • namenode










    share|improve this question

























      0












      0








      0








      I recently followed article https://www.quora.com/How-do-I-install-Hadoop-2-8-2-on-Windows-10-for-practice, and tried to run Hadoop on my Windows 10 machine (i7, 16GB RAM). It started correctly - no issues. But when I installed Docker, which inturn enabled Hyper-V, I started to get following failure while starting NodeManager



      18/12/19 21:29:31 INFO ipc.Server: IPC Server listener on 8040: starting
      18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
      18/12/19 21:29:31 INFO localizer.ResourceLocalizationService: Attempting to initialize /tmp/hadoop-username/nm-local-dir
      18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
      18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Failed to setup local dir /tmp/hadoop-username/nm-local-dir, which was marked as good.
      org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
      ...


      Following services start without any issues




      • ResourceManager

      • datanode

      • namenode










      share|improve this question














      I recently followed article https://www.quora.com/How-do-I-install-Hadoop-2-8-2-on-Windows-10-for-practice, and tried to run Hadoop on my Windows 10 machine (i7, 16GB RAM). It started correctly - no issues. But when I installed Docker, which inturn enabled Hyper-V, I started to get following failure while starting NodeManager



      18/12/19 21:29:31 INFO ipc.Server: IPC Server listener on 8040: starting
      18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
      18/12/19 21:29:31 INFO localizer.ResourceLocalizationService: Attempting to initialize /tmp/hadoop-username/nm-local-dir
      18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
      18/12/19 21:29:31 WARN localizer.ResourceLocalizationService: Failed to setup local dir /tmp/hadoop-username/nm-local-dir, which was marked as good.
      org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Permissions incorrectly set for dir /tmp/hadoop-username/nm-local-dir/usercache, should be rwxr-xr-x, actual value = rw-rw-rw-
      ...


      Following services start without any issues




      • ResourceManager

      • datanode

      • namenode







      hadoop






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 19 '18 at 21:48









      AlfredSKLAlfredSKL

      11




      11






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Changing yarn-site.xml to this worked for me. In my case was due to Windows Domain not reachable.



          <configuration>

          <!-- Site specific YARN configuration properties -->
          <property>
          <name>yarn.resourcemanager.hostname</name>
          <value>0.0.0.0</value>
          </property>
          <property>
          <name>yarn.nodemanager.local-dirs</name>
          <value>c:myhadoop-2.7.1tmp-nm</value>
          </property>

          <property>
          <name>yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage</name>
          <value>98.5</value>
          </property>
          </configuration>





          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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%2fsuperuser.com%2fquestions%2f1386060%2frunning-hadoop-2-8-0-on-windows-10-yarnruntimeexception-permissions-incorrectly%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














            Changing yarn-site.xml to this worked for me. In my case was due to Windows Domain not reachable.



            <configuration>

            <!-- Site specific YARN configuration properties -->
            <property>
            <name>yarn.resourcemanager.hostname</name>
            <value>0.0.0.0</value>
            </property>
            <property>
            <name>yarn.nodemanager.local-dirs</name>
            <value>c:myhadoop-2.7.1tmp-nm</value>
            </property>

            <property>
            <name>yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage</name>
            <value>98.5</value>
            </property>
            </configuration>





            share|improve this answer




























              0














              Changing yarn-site.xml to this worked for me. In my case was due to Windows Domain not reachable.



              <configuration>

              <!-- Site specific YARN configuration properties -->
              <property>
              <name>yarn.resourcemanager.hostname</name>
              <value>0.0.0.0</value>
              </property>
              <property>
              <name>yarn.nodemanager.local-dirs</name>
              <value>c:myhadoop-2.7.1tmp-nm</value>
              </property>

              <property>
              <name>yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage</name>
              <value>98.5</value>
              </property>
              </configuration>





              share|improve this answer


























                0












                0








                0







                Changing yarn-site.xml to this worked for me. In my case was due to Windows Domain not reachable.



                <configuration>

                <!-- Site specific YARN configuration properties -->
                <property>
                <name>yarn.resourcemanager.hostname</name>
                <value>0.0.0.0</value>
                </property>
                <property>
                <name>yarn.nodemanager.local-dirs</name>
                <value>c:myhadoop-2.7.1tmp-nm</value>
                </property>

                <property>
                <name>yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage</name>
                <value>98.5</value>
                </property>
                </configuration>





                share|improve this answer













                Changing yarn-site.xml to this worked for me. In my case was due to Windows Domain not reachable.



                <configuration>

                <!-- Site specific YARN configuration properties -->
                <property>
                <name>yarn.resourcemanager.hostname</name>
                <value>0.0.0.0</value>
                </property>
                <property>
                <name>yarn.nodemanager.local-dirs</name>
                <value>c:myhadoop-2.7.1tmp-nm</value>
                </property>

                <property>
                <name>yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage</name>
                <value>98.5</value>
                </property>
                </configuration>






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 14 at 10:25









                divyesh Puridivyesh Puri

                1




                1






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1386060%2frunning-hadoop-2-8-0-on-windows-10-yarnruntimeexception-permissions-incorrectly%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







                    Popular posts from this blog

                    Terni

                    A new problem with tex4ht and tikz

                    Sun Ra