ndb - bug#27087

  Make sure not to handle API_FAILREQ if it's already handled
parent 5ea42fb2
......@@ -578,6 +578,18 @@ void Suma::execAPI_FAILREQ(Signal* signal)
return;
}
if (c_failedApiNodes.get(failedApiNode))
{
jam();
return;
}
if (!c_subscriber_nodes.get(failedApiNode))
{
jam();
return;
}
c_failedApiNodes.set(failedApiNode);
c_connected_nodes.clear(failedApiNode);
bool found = removeSubscribersOnNode(signal, failedApiNode);
......@@ -591,9 +603,12 @@ void Suma::execAPI_FAILREQ(Signal* signal)
Ptr<Gcp_record> gcp;
for(c_gcp_list.first(gcp); !gcp.isNull(); c_gcp_list.next(gcp))
{
jam();
ack->rep.gci = gcp.p->m_gci;
if(gcp.p->m_subscribers.get(failedApiNode))
{
jam();
gcp.p->m_subscribers.clear(failedApiNode);
ack->rep.senderRef = numberToRef(0, failedApiNode);
sendSignal(SUMA_REF, GSN_SUB_GCP_COMPLETE_ACK, signal,
SubGcpCompleteAck::SignalLength, JBB);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment