1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ndb - bug#27087

Browse Source 
Make sure not to handle API_FAILREQ if it's already handled
This commit is contained in:
jonas@perch.ndb.mysql.com 2007-03-14 11:22:11 +01:00
parent 5ea42fb2ea
commit 820901f928
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
storage/ndb/src/kernel/blocks/suma/Suma.cpp
View File

@ -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);