data corruption issues after performing high-frequency write operations into GridDB. The write-ahead log (WAL) appears to be corrupted, and some of the recently inserted records are lost, or the data is inconsistent.

I enabled transaction mode (conn.setTransactionMode(true)) to ensure that all insert operations are handled atomically. I performed bulk inserts in batches, and after each batch, I committed the transaction using connmit(). In case of any failure, I implemented a rollback (conn.rollback()) to ensure that no partial data is committed.

I expect no write-ahead log (WAL) corruption and data consistency during high-frequency inserts. By using transactions, the data should either be fully written or not written at all, and no partial or corrupted records should remain in the database. The system should handle bulk inserts reliably without any data integrity issues.

:import com.toshiba.mwcloud.gs.*;

public class GridDBWriteLog {
    public static void main(String[] args) {
        try (Connection conn = GridDBFactory.getInstance().getConnection("localhost", 10001, "admin", "admin")) {
            conn.setTransactionMode(true);
            conn.begin();
            for (int i = 0; i < 1000; i++) {
                Entry entry = new Entry();
                entry.setField("timestamp", System.currentTimeMillis());
                entry.setField("device_id", "device_" + i);
                conn.insert(entry);
            }
            connmit(); // Ensure data consistency
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
}