You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@slider.apache.org by Sherry G <sx...@yahoo.com.INVALID> on 2015/10/13 20:25:18 UTC

Fix Slider website typos

Hi,I have been reading the Slider website, in particular, https://slider.incubator.apache.org/docs/configuration/resources.html, and found a few minor typos.  Are the website sources kept in git?
1. Slider reacts to a failed container by requesting a new container from YARN, preferably on a host that has already hosted an instance of that role. Once the container is allocated, slider will redeploy an instance of the component. As it may time for YARN to have the resources to allocate the container, it may take some time for the replacement to be instantiated.

2. "components": {
    "HBASE_MASTER": {
      "yarn.role.priority": "1",
      "yarn.component.instances": "1",
      "yarn.placement.escalate.seconds": "10"
    },
    "HBASE_REGIONSERVER": {
      "yarn.role.priority": "2",
      "yarn.component.instances": "10",
      "yarn.placement.escalate.seconds": "600"
    },
    "slider-appmaster": {
    }

This declares that the HBASE_MASTER placement should be escalated after one second, but that that HBASE_REGIONSERVER instances should have an escalation timeout of 600 seconds —ten minutes.
3.
1.    Escalation goes directory from "specific node" to "anywhere in cluster"; it does not have any intermediate "same-rack" policy.

4. The resources.json file include specifications the labels to be used when allocating containers for the components. The details of the YARN Label feature can be found at YARN-796.

Fix Slider website typos

Posted by Sherry G <sx...@yahoo.com.INVALID>.

Hi,I have been reading the Slider website, in particular, https://slider.incubator.apache.org/docs/configuration/resources.html, and found a few minor typos.  Are the website sources kept in git?
1. Slider reacts to a failed container by requesting a new container from YARN, preferably on a host that has already hosted an instance of that role. Once the container is allocated, slider will redeploy an instance of the component. As it may time for YARN to have the resources to allocate the container, it may take some time for the replacement to be instantiated.

2. "components": {
    "HBASE_MASTER": {
      "yarn.role.priority": "1",
      "yarn.component.instances": "1",
      "yarn.placement.escalate.seconds": "10"
    },
    "HBASE_REGIONSERVER": {
      "yarn.role.priority": "2",
      "yarn.component.instances": "10",
      "yarn.placement.escalate.seconds": "600"
    },
    "slider-appmaster": {
    }

This declares that the HBASE_MASTER placement should be escalated after one second, but that that HBASE_REGIONSERVER instances should have an escalation timeout of 600 seconds —ten minutes.
3.
1.    Escalation goes directory from "specific node" to "anywhere in cluster"; it does not have any intermediate "same-rack" policy.

4. The resources.json file include specifications the labels to be used when allocating containers for the components. The details of the YARN Label feature can be found at YARN-796.