High Availability Guide : Administering and configuring HotStandby : Special considerations for using solidDB® with HotStandby : Transaction isolation level and in-memory tables
  
Transaction isolation level and in-memory tables
If you are connected to the Secondary and you are reading data from in-memory tables, the transaction isolation level is automatically set to READ COMMITTED. The transaction level is READ COMMITTED even if you have specified it as REPEATABLE READ, or SERIALIZABLE.
Additionally, if load balancing is used, the isolation level is READ COMMITTED by default.
See also
Special considerations for using solidDB® with HotStandby