Dremio service crashes

When querying data from dremio via jdbc (with ontop) dremio crashes and restarts

/var/log/messages:
dremio: LLVM ERROR: 64-bit code requested on a subtarget that doesn’t support it!
systemd: dremio.service: main process exited, code=exited, status=1/FAILURE
systemd: Unit dremio.service entered failed state.
systemd: dremio.service failed.
systemd: dremio.service holdoff time over, scheduling restart.
systemd: Stopped Dremio Daemon Server.
systemd: Started Dremio Daemon Server.

ontop-log:
INFO 19210 — [ Client-1] c.com.dremio.sabot.rpc.user.UserClient : [USER]: Channel closed null <–> null (user client)
INFO 19210 — [ Client-1] c.com.dremio.sabot.rpc.user.UserClient : [USER]: Channel closed null <–> null (user client)
INFO 19210 — [ Client-1] c.c.d.sabot.rpc.user.QueryResultHandler : User Error Occurred [ErrorId: 5174c084-6e50-45e5-bc3d-95f00f55a461]
cdjd.com.dremio.common.exceptions.UserException: Connection null <–> null (user client) closed unexpectedly. SabotNode down?

I am running Dremio 4.3.1 but experienced the same issue with version 4.9.1

@Muffex

This is most likely because, Dremio running on a machine that we dont support

Can you provide us Hardware and OS details

Thanks
Bali

Thanks for your answer.

OS-Info:
hostnamectl
Static hostname: hostname
Icon name: computer-vm
Chassis: vm
Virtualization: kvm
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-1127.19.1.el7.x86_64
Architecture: x86-64

HW-Info of VM:
sudo lshw -short
H/W path Device Class Description
system KVM
/0 bus Motherboard
/0/0 memory 96KiB BIOS
/0/400 processor QEMU Virtual CPU version 2.5+

/0/1000 memory 48GiB System Memory
/0/1000/0 memory 16GiB DIMM RAM

/0/100 bridge 82G33/G31/P35/P31 Express DRAM Controller
/0/100/1 display QXL paravirtual graphic card
/0/100/2 bridge QEMU PCIe Root port
/0/100/2/0 network Virtio network device
/0/100/2/0/0 eth0 network Ethernet interface
/0/100/2.1 bridge QEMU PCIe Root port
/0/100/2.1/0 bus QEMU XHCI Host Controller
/0/100/2.1/0/0 usb1 bus xHCI Host Controller
/0/100/2.1/0/0/1 input QEMU USB Tablet
/0/100/2.1/0/1 usb2 bus xHCI Host Controller
/0/100/2.2 bridge QEMU PCIe Root port
/0/100/2.2/0 communication Virtio console
/0/100/2.2/0/0 generic Virtual I/O device
/0/100/2.3 bridge QEMU PCIe Root port
/0/100/2.3/0 storage Virtio block device
/0/100/2.3/0/0 /dev/vda disk 536GB Virtual I/O device
/0/100/2.3/0/0/1 /dev/vda1 volume 1GiB Linux filesystem partition
/0/100/2.3/0/0/2 /dev/vda2 volume 4GiB Linux swap volume
/0/100/2.3/0/0/3 /dev/vda3 volume 494GiB Linux filesystem partition
/0/100/2.4 bridge QEMU PCIe Root port
/0/100/2.4/0 generic Virtio memory balloon
/0/100/2.4/0/0 generic Virtual I/O device
/0/100/2.5 bridge QEMU PCIe Root port
/0/100/2.5/0 generic Virtio RNG
/0/100/2.5/0/0 generic Virtual I/O device
/0/100/2.6 bridge QEMU PCIe Root port
/0/100/1b multimedia 82801I (ICH9 Family) HD Audio Controller
/0/100/1f bridge 82801IB (ICH9) LPC Interface Controller
/0/100/1f.2 scsi0 storage 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode]
/0/100/1f.2/0.0.0 /dev/cdrom disk QEMU DVD-ROM
/0/100/1f.3 bus 82801I (ICH9 Family) SMBus Controller
/0/1 system PnP device PNP0b00
/0/2 input PnP device PNP0303
/0/3 input PnP device PNP0f13
/0/4 communication PnP device PNP0501#

Do you see any limitations?

@Muffex

We have known issues with “QEMU”, is that your only choice?

Thanks
Bali

@balaji.ramaswamy

Thanks for your answer. Is there any workaround?
If not. Which system should be used instead?

regards

@Muffex

Workaround is to turn off Gandiva but can cause slower query execution

Thanks
Bali

@balaji.ramaswamy

If I’m honest, I have never heard of Gandiva. How can it be turned off?

regards

@Muffex

Stringly recommend to use a cluster that is not a “QEMU” architecture but to confirm this is the issue you can turn off Gandiva by setting “exec.preferred.codegenerator” to value “java” under admin-support-support key

1 Like

After setting this property the queries work.
Thank you very much.