You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the MockBatchDeleter, occasionally it seems with MapReduce tests, was throwing ConcurrentModificationException when purging the MockInstance. This is because the mock instance is backed by TreeMap. Without looking into this deeper, what probably needs to happen is that we should swap out the TreeMap with some sort of ConcurrentTreeMap. Java has a ConcurrentHashMap, but we need to support natural ordering via a TreeMap.
In the meantime, the MockBatchDeleter catches the ConcurrentModificationException and ignores it. It seems to work fine for now, but may present an issue in the future.
The text was updated successfully, but these errors were encountered:
In the MockBatchDeleter, occasionally it seems with MapReduce tests, was throwing ConcurrentModificationException when purging the MockInstance. This is because the mock instance is backed by TreeMap. Without looking into this deeper, what probably needs to happen is that we should swap out the TreeMap with some sort of ConcurrentTreeMap. Java has a ConcurrentHashMap, but we need to support natural ordering via a TreeMap.
In the meantime, the MockBatchDeleter catches the ConcurrentModificationException and ignores it. It seems to work fine for now, but may present an issue in the future.
The text was updated successfully, but these errors were encountered: