【问题标题】:Apache Ignite 2.1: Getting a "Conflicting type IDs" error after upgrading from 2.0Apache Ignite 2.1:从 2.0 升级后出现“冲突类型 ID”错误
【发布时间】:2018-01-11 16:00:19
【问题描述】:

从 Apache Ignite 2.0 升级到 2.1 (.Net) 后,我收到错误“冲突类型 ID [type1='Row', type2='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());
}

【问题讨论】:

    标签: c# ignite


    【解决方案1】:

    我已经复制并提交了错误:https://issues.apache.org/jira/browse/IGNITE-5931

    这是一个竞态条件,我认为它也存在于 2.0 中(这段代码在 2.1 和 2.0 中是相同的)。还有两个地方可以正确完成类似的检查,期待多线程场景,但这个被遗忘了。

    解决方法一:在BinaryConfiguration注册类型:

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

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

    【讨论】:

      猜你喜欢
      • 2018-04-06
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2015-08-31
      • 1970-01-01
      • 2014-06-13
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多