<p dir="auto">Right now the cassandra docs use a ReplicationController. I think it would be good to update the doc to mention using daemon sets as a valid way to place a single cassandra node on each of the kubernetes nodes, a more realistic deployment method.</p>
<p dir="auto">See <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="110533249" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/15324" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/15324/hovercard" href="https://github.com/kubernetes/kubernetes/issues/15324">#15324</a></p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ kubectl version
Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;3&quot;, GitVersion:&quot;v1.3.6&quot;, GitCommit:&quot;ae4550cc9c89a593bcda6678df201db1b208133b&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-08-26T18:13:23Z&quot;, GoVersion:&quot;go1.6.2&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.6&quot;, GitCommit:&quot;e569a27d02001e343cb68086bc06d47804f62af6&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-11-12T05:16:27Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}"><pre class="notranslate"><code class="notranslate">$ kubectl version
Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.6", GitCommit:"ae4550cc9c89a593bcda6678df201db1b208133b", GitTreeState:"clean", BuildDate:"2016-08-26T18:13:23Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.6", GitCommit:"e569a27d02001e343cb68086bc06d47804f62af6", GitTreeState:"clean", BuildDate:"2016-11-12T05:16:27Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: GKE</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): default</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
I was trying to reproduce <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="182915151" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/34772" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/34772/hovercard" href="https://github.com/kubernetes/kubernetes/issues/34772">#34772</a> using <a href="https://github.com/kubernetes/kubernetes/issues/34772#issuecomment-260594667" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/34772/hovercard">these instructions</a>. Due to bug in scheduler we were assigning too many pods per node. In most cases kubelet was correctly discarding them by marking them as <code class="notranslate">OutOfcpu</code>. However two strange things happened:</p>
<ul dir="auto">
<li>upon kubelet restart, it tried to re-add all such <code class="notranslate">OutOfcpu</code> pods, run predicate check for them etc.</li>
<li>for two pods that were incorrectly assigned (due to scheduler bug) during kubelet restart kubelet completely ignored them - they are still pending, with node assigned for 12h.</li>
</ul>
<p dir="auto">I have a cluster that I can add someone to investigate.</p>
<p dir="auto"><strong>What you expected to happen</strong>:</p>
<ul dir="auto">
<li><code class="notranslate">OutOfcpu</code> pods should not be retried after restart</li>
<li>new pods, assigned during kubelet restart, should be discarded with <code class="notranslate">OutOfcpu</code> error.</li>
</ul>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto">Run <a href="https://github.com/kubernetes/kubernetes/issues/34772#issuecomment-260594667" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/34772/hovercard">these instructions</a>.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto">Marking as <code class="notranslate">release-blocker</code> until it's triaged by node team.</p>