ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Veselovsky <iveselovs...@gridgain.com>
Subject Re: igfs-meta behavior when node restarts
Date Mon, 29 May 2017 16:10:38 GMT
Enabling debug logging level in class
org.apache.ignite.internal.processors.igfs.IgfsImpl can give tracing of all
the IGFS operations performed -- this can help to track this issue down.
Many operations in IGFS are implemented using "retry" logic , like the

while (true) {
   try (GridNearTxLocal tx = startTx()) {
         // Lock participants.
         Map<IgniteUuid, IgfsEntryInfo> lockInfos = lockIds(allIds); 

         if (!checkSomeIntegrity(....))

        // do smth ....


, so they may experience contention (staring and abandoning a transaction
many times per one operation) if some overlapping operations are attempted

View this message in context: http://apache-ignite-users.70518.x6.nabble.com/igfs-meta-behavior-when-node-restarts-tp13155p13206.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message