このコンテンツは選択した言語では利用できません。
Chapter 4. Known Issues
The following issues are known to exist in Red Hat JBoss Data Grid 6.2.1 and will be fixed in a subsequent release.
- BZ#881080 - Silence SuspectExceptions
- SuspectExceptions are raised when nodes are shutting down, which is normal and expected, since a suspect node is an unresponsive node. As a result, a SuspectException ERROR is written in the logs. There is currently no fix for this issue. The SuspectExceptions will not be logged in a future version of Red Hat JBoss Data Grid. The SuspectExceptions do not affect data integrity.
- BZ#881791 - Special characters in file path to JDG server are causing problems
- Using special characters in directory paths can cause problems when starting Red Hat JBoss Data Grid server. The JBoss Data Grid server either fails to start or a configuration file for logging capabilities cannot be loaded properly. Special characters include spaces, # (hash sign), ! (exclamation mark), % (percentage sign), $ (dollar sign). This bug causes the JBoss Data Grid server to fail to start properly.Avoiding the use of special characters will stop this problem occurring, allowing JBoss Data Grid server to start properly.
- BZ#1012036 - RELAY2 logs error when site unreachable
- When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort), and even with ignore policy the log is filled with errors.
- BZ#1013001 - [ISPN-3375] Map/Reduce jobs with small value sizes fail because of timeouts putting intermediate keys into the cache
- When a Map/Reduce task is executed against a cache with many small values, the task may experience TimeoutExceptions while trying to write the intermediate results to the cache.As a result, when these exceptions occur, the task fails.There are several things the user can do to try and alleviate this issue:
- Use larger values in the cache where the Map/Reduce task is executed.
- Use a collator and/or a combiner on the Map/Reduce task if this is possible.
- Configure the size of the intermediate chunks written to the cache using the state transfer chunkSize parameter.
- BZ#1043434 - L1 entry added by ST when already invalidated
- In distributed cache mode with L1 enabled and
onRehash=true, when an entry is overwritten during state transfer, the overwrite may be ignored. This node will then report an outdated value of the entry, and after L1 timeout this entry will be completely removed.As a workaround, use L1 withonRehash=false.
