ApacheIgnite2.1:从2.0升级到“冲突类型ID”错误

Question

在从ApacheIgnite2.0升级到2.1 (typeId=113114)之后，我得到了错误"Conflicting 1=‘Row’，type 2=‘Row’，typeId=113114“。升级后我没有修改任何代码，所以我想知道如何创建和使用动态二进制对象的期望是否发生了变化？我看了一下AddType方法。也许它应该返回而不是抛出，也许这个方法的名称是误导的，它应该是GetOrAddType？

AddType方法：https://github.com/apache/ignite/blob/efd299f401ea34e040037c76be0c9f86e0e8e239/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Binary/Marshaller.cs#L667

堆栈跟踪：

   at Apache.Ignite.Core.Impl.Binary.Marshaller.ThrowConflictingTypeError(Object type1, Object type2, Int32 typeId)
   at Apache.Ignite.Core.Impl.Binary.Marshaller.AddType(Type type, Int32 typeId, String typeName, Boolean userType, Boolean keepDeserialized, IBinaryNameMapper nameMapper, IBinaryIdMapper idMapper, IBinarySerializerInternal serializer, String affKeyFieldName, Boolean isEnum)
   at Apache.Ignite.Core.Impl.Binary.Marshaller.AddUserType(BinaryTypeConfiguration typeCfg, TypeResolver typeResolver)
   at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Boolean userType, Int32 typeId, Boolean requiresType, String typeName, Type knownType)
   at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(String typeName)
   at Apache.Ignite.Core.Impl.Binary.Binary.GetBuilder(String typeName)
   at MyCompany.DataFabric.Core.CacheManagers.Table.RowCacheManager.BuildRow(Int64 rowNumber, String row, Boolean setColumnFields) in C:\Users\me\Documents\GitLab\Platform\Core\CacheManagers\Table\RowCacheManager.cs:line 140
   at MyCompany.DataFabric.Core.CacheManagers.Table.RowCacheManager.<>c__DisplayClass26_1.<WriteAsync>b__1(KeyValuePair`2 r) in C:\Users\me\Documents\GitLab\Platform\Core\CacheManagers\Table\RowCacheManager.cs:line 128
   at System.Threading.Tasks.Parallel.<>c__DisplayClass42_0`2.<PartitionerForEachWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)
   at System.Threading.Tasks.Task.<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(Object )

这就是我的代码的样子：

public async Task WriteAsync(IEnumerable<string> rows, long startRowNum = 0) {
    // Create the cache if it doesn't exist, yet
    await this.GetOrCreateRowCache();

    using (var ds = m_ignite.GetDataStreamer<string, object>(CacheName).WithKeepBinary<string, IBinaryObject>()) {
        try {
            ds.AllowOverwrite = true;
            ds.Receiver = new RowStreamReceiver {
                TableId = TableId
            };

            Parallel.ForEach(rows.Select((r, i) => new KeyValuePair<long, string>(i, r)), r => {
                var rowNum = r.Key + startRowNum;
                if (rowNum % 10000 == 0) {
                    Console.WriteLine($"Put [Row: {r.Key}, Thread: {Thread.CurrentThread.ManagedThreadId}]");
                }
                var pair = BuildRow(rowNum, r.Value, false);
                // ReSharper disable once AccessToDisposedClosure
                ds.AddData(pair);
            });
        } finally {
            Console.WriteLine("Flushing");
            ds.Flush();
        }
    }
}

public KeyValuePair<string, IBinaryObject> BuildRow(long rowNumber, string row, bool setColumnFields = true) {
    var builder = m_ignite.GetBinary().GetBuilder(TypeName);

    var rowId = row.GetHashString();
    builder.SetField(PrimaryKeyName, rowId);
    builder.SetField(RowNumberName, rowNumber);
    builder.SetField(RawName, row);

    if (setColumnFields) {
        SetColumnFields(m_table, row, builder);
    }

    return new KeyValuePair<string, IBinaryObject>(rowId, builder.Build());
}

Answer 1

我复制并归档了这个bug：https://issues.apache.org/jira/browse/IGNITE-5931

这是一种竞争条件，我认为2.0中也存在这种情况(这段代码在2.1和2.0中是相同的)。还有另外两个地方可以正确地进行类似的检查，期望出现多线程场景，但这一次被遗忘了。

解决方案1：在BinaryConfiguration中注册类型

        var cfg = new IgniteConfiguration
        {
            BinaryConfiguration = new BinaryConfiguration
            {
                Types = new[] {"Row"}
            }
        };

解决方案2：同步对GetBuilder方法的访问(将其放入锁中)。实际处理不必处于锁定状态，因此性能不会受到影响。