Bug#25777337 TC BLOCK DOES NOT HANDLE 'DROPPED' LONG 'TRANSID_AI SIGNALS

Handling of TRANSID_AI signals 'dropped' due to
'out of long signal message buffers' were not implemented
in Dbtc::execSIGNAL_DROPPED_REP(). Such signals could (only)
come from unique index operations.

This patch introduce handling of such dropped TRANSID_AI
signals by aborting the TcIndexOperation.

Author: Ole John Aske

storage/ndb/src/kernel/blocks/dbtc/DbtcMain.cpp

@@ -1,4 +1,4 @@
-/* Copyright (c) 2003, 2016, Oracle and/or its affiliates. All rights reserved.
+/* Copyright (c) 2003, 2017, Oracle and/or its affiliates. All rights reserved.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -4515,6 +4515,36 @@ void Dbtc::execSIGNAL_DROPPED_REP(Signal* signal)
                signal, ScanTabRef::SignalLength, JBB);
     break;
   }
+  case GSN_TRANSID_AI: //TUP -> TC
+  {
+    jam();
+    /**
+     * TRANSID_AI is received as a result of performing a read on 
+     * the index table as part of a (unique) index operation.
+     */
+    const TransIdAI * const truncatedTransIdAI = 
+      reinterpret_cast<const TransIdAI*>(&rep->originalData[0]);
+
+    TcIndexOperationPtr indexOpPtr;
+    indexOpPtr.i = truncatedTransIdAI->connectPtr;
+    TcIndexOperation* indexOp = c_theIndexOperationPool.getPtr(indexOpPtr.i);
+    indexOpPtr.p = indexOp;
+    if (indexOp == NULL) {
+      jam();
+      // Missing index operation - ignore
+      break;
+    }
+
+    /* No more TransIdAI will arrive, abort */
+    apiConnectptr.i = indexOp->connectionIndex;
+    ptrCheckGuard(apiConnectptr, capiConnectFilesize, apiConnectRecord);
+
+    terrorCode = ZGET_DATAREC_ERROR;
+    abortErrorLab(signal);
+    break;
+  }
+  case GSN_TRANSID_AI_R:  //TODO
+    jam();
   default:
     jam();
     /* Don't expect dropped signals for other GSNs,