scylla-ami-setup: I/O Scheduler is not properly configured

Created on 21 Jun 2018 · 6Comments · Source: scylladb/scylla

Installation details
Scylla version (or git commit hash): 666.development-0.20180620.6572917fd
Cluster size: 1
OS (RHEL/CentOS/Ubuntu/AWS AMI): ami-ad99ccd2
Instance type: c3.large

test job: job/scylla-master-ami-test/label=muninn/239/

[centos@ip-10-136-170-152 ~]$ sudo systemctl status scylla-server -l
● scylla-server.service - Scylla Server
   Loaded: loaded (/usr/lib/systemd/system/scylla-server.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/scylla-server.service.d
           └─capabilities.conf
   Active: failed (Result: exit-code) since Thu 2018-06-21 08:10:42 UTC; 5min ago
  Process: 1688 ExecStopPost=/usr/lib/scylla/scylla_stop (code=exited, status=0/SUCCESS)
  Process: 1681 ExecStart=/usr/bin/scylla $SCYLLA_ARGS $SEASTAR_IO $DEV_MODE $CPUSET (code=exited, status=1/FAILURE)
  Process: 1625 ExecStartPre=/usr/lib/scylla/scylla_prepare (code=exited, status=0/SUCCESS)
 Main PID: 1681 (code=exited, status=1/FAILURE)
   Status: "starting per-shard database core"

Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: Scylla version 666.development-0.20180620.6572917fd starting ...
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]:  [shard 0] snitch_logger - Ec2Snitch using region: us-east, zone: 1c.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]:  [shard 0] init - Scylla API server listening on 127.0.0.1:10000 ...
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]:  [shard 0] database - Row: max_vector_size: 32, internal_count: 5
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]:  [shard 1] database - Row: max_vector_size: 32, internal_count: 5
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]:  [shard 0] init - I/O Scheduler is not properly configured! This is a non-supported setup, and performance is expected to be unpredictably bad.
                                                              Reason found: none of --max-io-requests, --io-properties and --io-properties-file are set.
                                                             To properly configure the I/O Scheduler, run the scylla_io_setup utility shipped with Scylla.
                                                             To ignore this, see the developer_mode configuration option.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: scylla-server.service: main process exited, code=exited, status=1/FAILURE
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: Failed to start Scylla Server.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: Unit scylla-server.service entered failed state.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: scylla-server.service failed.

[centos@ip-10-136-170-152 ~]$ cat /etc/scylla.d/io.conf 
# DO NO EDIT
# This file should be automatically configure by scylla_io_setup
#
# SEASTAR_IO="--max-io-requests=1 --num-io-queues=1"

[centos@ip-10-136-170-152 ~]$ sudo systemctl status scylla-ami-setup
● scylla-ami-setup.service - Scylla AMI Setup
   Loaded: loaded (/usr/lib/systemd/system/scylla-ami-setup.service; enabled; vendor preset: disabled)
   Active: active (exited) since Thu 2018-06-21 08:10:36 UTC; 4min 9s ago
  Process: 1281 ExecStart=/usr/lib/scylla/scylla-ami/scylla_ami_setup (code=exited, status=0/SUCCESS)
 Main PID: 1281 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/scylla-ami-setup.service

Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       crc=1        finobt=0, sparse=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: data     =                       bsize=4096   blocks=7991296, imaxpct=25
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       sunit=256    swidth=512 blks
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: log      =internal log           bsize=4096   blocks=3904, version=2
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       sectsz=512   sunit=8 blks, lazy-count=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: realtime =none                   extsz=4096   blocks=0, rtextents=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] RAID Array containing ['xvdb', 'xvdc'] not found. Creating...
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal systemd[1]: Started Scylla AMI Setup.


[centos@ip-10-136-170-152 ~]$ journalctl -u scylla-ami-setup
-- Logs begin at Thu 2018-06-21 08:09:56 UTC, end at Thu 2018-06-21 08:14:46 UTC. --
Jun 21 08:10:15 ip-172-30-0-201.ec2.internal systemd[1]: Starting Scylla AMI Setup...
Jun 21 08:10:16 ip-172-30-0-201.ec2.internal scylla_ami_setup[1281]: Setting parameters on /etc/sysconfig/scylla-server
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: Waiting for cloud-init to finish...
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] No userdata found. Starting 1 node clusters, by default.
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using instance type: c3.large
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:instance-type: c3.large
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:local-ipv4: 10.136.170.152
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:public-hostname: ec2-54-90-128-15.compute-1.amazonaws.com
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:ami-launch-index: 0
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:reservation-id: r-0c33cbc4c85b3f8d5
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using cluster name: Test Cluster - No AMI Parameters
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using cluster size: 1
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using seed indexes: [0, 1, 1]
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Reflector loop...
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] 06/21/18-08:10:29 Reflector: Received 1 of 1 responses from: [u'10.136.170.152']
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] scylla.yaml configured.
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: Creating RAID0 for scylla using 2 disk(s): /dev/xvdb /dev/xvdc
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: /dev/xvdb does not supported TRIM, skipping blkdiscard...
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: /dev/xvdc does not supported TRIM, skipping blkdiscard...
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: /dev/xvdb appears to contain an ext2fs file system
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: size=15996416K  mtime=Thu Jan  1 00:00:00 1970
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: /dev/xvdc appears to contain an ext2fs file system
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: size=15996416K  mtime=Thu Jan  1 00:00:00 1970
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: creation continuing despite oddities due to --run
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: Defaulting to version 1.2 metadata
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: array /dev/md0 started.
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: meta-data=/dev/md0               isize=512    agcount=16, agsize=499456 blks
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       sectsz=512   attr=2, projid32bit=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       crc=1        finobt=0, sparse=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: data     =                       bsize=4096   blocks=7991296, imaxpct=25
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       sunit=256    swidth=512 blks
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: log      =internal log           bsize=4096   blocks=3904, version=2
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: =                       sectsz=512   sunit=8 blks, lazy-count=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: realtime =none                   extsz=4096   blocks=0, rtextents=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] RAID Array containing ['xvdb', 'xvdc'] not found. Creating...
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal systemd[1]: Started Scylla AMI Setup.

AWS bug

Source

amoskong

👍1

Most helpful comment

Manually execute scylla_io_setup, it succeeds. And scylla-server can be started after that.

[centos@ip-10-136-170-152 ~]$ sudo scylla_io_setup 
tuning /sys/devices/virtual/block/md0
already tuned: /sys/devices/virtual/block/md0/queue/nomerges
tuning /sys/devices/vbd-51744/block/xvdc
already tuned: /sys/devices/vbd-51744/block/xvdc/queue/nomerges
tuning /sys/devices/vbd-51728/block/xvdb
already tuned: /sys/devices/vbd-51728/block/xvdb/queue/nomerges
INFO  2018-06-21 08:19:05,445 [shard 0] iotune - /var/lib/scylla/data passed sanity checks
Measuring sequential write bandwidth: 346 MB/s
Measuring sequential read bandwidth: 898 MB/s
Measuring random write IOPS: 69761 IOPS
Measuring random read IOPS: 81890 IOPS
Recommended --num-io-queues: 2
[centos@ip-10-136-170-152 ~]$ echo $?
0
[centos@ip-10-136-170-152 ~]$ cat /etc/scylla.d/io.conf 
SEASTAR_IO="--num-io-queues=2 --io-properties-file=/etc/scylla.d/io_properties.yaml"

[centos@ip-10-136-170-152 ~]$ sudo systemctl restart scylla-server
[centos@ip-10-136-170-152 ~]$ nodetool status
Datacenter: us-east
===================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address         Load       Tokens       Owns    Host ID                               Rack
UN  10.136.170.152  443.96 KB  256          ?       23a83a25-8b88-4db7-b6a6-dab26939609d  1c

amoskong on 21 Jun 2018

👍2

All 6 comments

Manually execute scylla_io_setup, it succeeds. And scylla-server can be started after that.

[centos@ip-10-136-170-152 ~]$ sudo scylla_io_setup 
tuning /sys/devices/virtual/block/md0
already tuned: /sys/devices/virtual/block/md0/queue/nomerges
tuning /sys/devices/vbd-51744/block/xvdc
already tuned: /sys/devices/vbd-51744/block/xvdc/queue/nomerges
tuning /sys/devices/vbd-51728/block/xvdb
already tuned: /sys/devices/vbd-51728/block/xvdb/queue/nomerges
INFO  2018-06-21 08:19:05,445 [shard 0] iotune - /var/lib/scylla/data passed sanity checks
Measuring sequential write bandwidth: 346 MB/s
Measuring sequential read bandwidth: 898 MB/s
Measuring random write IOPS: 69761 IOPS
Measuring random read IOPS: 81890 IOPS
Recommended --num-io-queues: 2
[centos@ip-10-136-170-152 ~]$ echo $?
0
[centos@ip-10-136-170-152 ~]$ cat /etc/scylla.d/io.conf 
SEASTAR_IO="--num-io-queues=2 --io-properties-file=/etc/scylla.d/io_properties.yaml"

[centos@ip-10-136-170-152 ~]$ sudo systemctl restart scylla-server
[centos@ip-10-136-170-152 ~]$ nodetool status
Datacenter: us-east
===================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address         Load       Tokens       Owns    Host ID                               Rack
UN  10.136.170.152  443.96 KB  256          ?       23a83a25-8b88-4db7-b6a6-dab26939609d  1c

amoskong on 21 Jun 2018

👍2

Which instance type is this ?

On Thu, Jun 21, 2018, 4:18 AM Amos Kong, notifications@github.com wrote:

Installation details
Scylla version (or git commit hash): 666.development-0.20180620.6572917fd
Cluster size: 1
OS (RHEL/CentOS/Ubuntu/AWS AMI): ami-ad99ccd2

[centos@ip-10-136-170-152 ~]$ sudo systemctl status scylla-server -l
● scylla-server.service - Scylla Server
Loaded: loaded (/usr/lib/systemd/system/scylla-server.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/scylla-server.service.d
└─capabilities.conf
Active: failed (Result: exit-code) since Thu 2018-06-21 08:10:42 UTC; 5min ago
Process: 1688 ExecStopPost=/usr/lib/scylla/scylla_stop (code=exited, status=0/SUCCESS)
Process: 1681 ExecStart=/usr/bin/scylla $SCYLLA_ARGS $SEASTAR_IO $DEV_MODE $CPUSET (code=exited, status=1/FAILURE)
Process: 1625 ExecStartPre=/usr/lib/scylla/scylla_prepare (code=exited, status=0/SUCCESS)
Main PID: 1681 (code=exited, status=1/FAILURE)
Status: "starting per-shard database core"

Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: Scylla version 666.development-0.20180620.6572917fd starting ...
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: [shard 0] snitch_logger - Ec2Snitch using region: us-east, zone: 1c.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: [shard 0] init - Scylla API server listening on 127.0.0.1:10000 ...
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: [shard 0] database - Row: max_vector_size: 32, internal_count: 5
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: [shard 1] database - Row: max_vector_size: 32, internal_count: 5
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal scylla[1681]: [shard 0] init - I/O Scheduler is not properly configured! This is a non-supported setup, and performance is expected to be unpredictably bad.
Reason found: none of --max-io-requests, --io-properties and --io-properties-file are set.
To properly configure the I/O Scheduler, run the scylla_io_setup utility shipped with Scylla.
To ignore this, see the developer_mode configuration option.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: scylla-server.service: main process exited, code=exited, status=1/FAILURE
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: Failed to start Scylla Server.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: Unit scylla-server.service entered failed state.
Jun 21 08:10:42 ip-10-136-170-152.ec2.internal systemd[1]: scylla-server.service failed.

[centos@ip-10-136-170-152 ~]$ cat /etc/scylla.d/io.conf

DO NO EDIT

This file should be automatically configure by scylla_io_setup

#

SEASTAR_IO="--max-io-requests=1 --num-io-queues=1"

[centos@ip-10-136-170-152 ~]$ sudo systemctl status scylla-ami-setup
● scylla-ami-setup.service - Scylla AMI Setup
Loaded: loaded (/usr/lib/systemd/system/scylla-ami-setup.service; enabled; vendor preset: disabled)
Active: active (exited) since Thu 2018-06-21 08:10:36 UTC; 4min 9s ago
Process: 1281 ExecStart=/usr/lib/scylla/scylla-ami/scylla_ami_setup (code=exited, status=0/SUCCESS)
Main PID: 1281 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/scylla-ami-setup.service

Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = crc=1 finobt=0, sparse=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: data = bsize=4096 blocks=7991296, imaxpct=25
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = sunit=256 swidth=512 blks
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: naming =version 2 bsize=4096 ascii-ci=0 ftype=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: log =internal log bsize=4096 blocks=3904, version=2
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = sectsz=512 sunit=8 blks, lazy-count=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: realtime =none extsz=4096 blocks=0, rtextents=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] RAID Array containing ['xvdb', 'xvdc'] not found. Creating...
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal systemd[1]: Started Scylla AMI Setup.

[centos@ip-10-136-170-152 ~]$ journalctl -u scylla-ami-setup
-- Logs begin at Thu 2018-06-21 08:09:56 UTC, end at Thu 2018-06-21 08:14:46 UTC. --
Jun 21 08:10:15 ip-172-30-0-201.ec2.internal systemd[1]: Starting Scylla AMI Setup...
Jun 21 08:10:16 ip-172-30-0-201.ec2.internal scylla_ami_setup[1281]: Setting parameters on /etc/sysconfig/scylla-server
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: Waiting for cloud-init to finish...
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] No userdata found. Starting 1 node clusters, by default.
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using instance type: c3.large
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:instance-type: c3.large
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:local-ipv4: 10.136.170.152
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:public-hostname: ec2-54-90-128-15.compute-1.amazonaws.com
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:ami-launch-index: 0
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] meta-data:reservation-id: r-0c33cbc4c85b3f8d5
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using cluster name: Test Cluster - No AMI Parameters
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using cluster size: 1
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Using seed indexes: [0, 1, 1]
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] Reflector loop...
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] 06/21/18-08:10:29 Reflector: Received 1 of 1 responses from: [u'10.136.170.152']
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] scylla.yaml configured.
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: Creating RAID0 for scylla using 2 disk(s): /dev/xvdb /dev/xvdc
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: /dev/xvdb does not supported TRIM, skipping blkdiscard...
Jun 21 08:10:29 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: /dev/xvdc does not supported TRIM, skipping blkdiscard...
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: /dev/xvdb appears to contain an ext2fs file system
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: size=15996416K mtime=Thu Jan 1 00:00:00 1970
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: /dev/xvdc appears to contain an ext2fs file system
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: size=15996416K mtime=Thu Jan 1 00:00:00 1970
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: creation continuing despite oddities due to --run
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: Defaulting to version 1.2 metadata
Jun 21 08:10:30 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: mdadm: array /dev/md0 started.
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: meta-data=/dev/md0 isize=512 agcount=16, agsize=499456 blks
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = sectsz=512 attr=2, projid32bit=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = crc=1 finobt=0, sparse=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: data = bsize=4096 blocks=7991296, imaxpct=25
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = sunit=256 swidth=512 blks
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: naming =version 2 bsize=4096 ascii-ci=0 ftype=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: log =internal log bsize=4096 blocks=3904, version=2
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: = sectsz=512 sunit=8 blks, lazy-count=1
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: realtime =none extsz=4096 blocks=0, rtextents=0
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: [INFO] RAID Array containing ['xvdb', 'xvdc'] not found. Creating...
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal scylla_ami_setup[1281]: kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
Jun 21 08:10:36 ip-10-136-170-152.ec2.internal systemd[1]: Started Scylla AMI Setup.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/scylla/issues/3538, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUNvQD-W53N78ZTmHyWAefer3M1KUgdks5t-1bngaJpZM4UxmjK
.

glommer on 21 Jun 2018

c3.large

On Thu, Jun 21, 2018 at 7:34 PM, Glauber Costa notifications@github.com
wrote:

Which instance type is this ?

amoskong on 21 Jun 2018

I try to reproduce and recheck the full scylla-server log (detail), this issue duplicates with #3508

amoskong on 22 Jun 2018

This issue still exist on the latest 2.3 AMI (ami-a1c2c7de) on c3.large.

Jul 22 11:11:48 ip-172-30-0-65.ec2.internal scylla[1630]:  [shard 0] init - I/O Scheduler is not properly configured! This is a non-supported setup, and performance is expected to be unpredictably bad.
                                                           Reason found: none of --max-io-requests, --io-properties and --io-properties-file are set.
                                                          To properly configure the I/O Scheduler, run the scylla_io_setup utility shipped with Scylla.
                                                          To ignore this, see the developer_mode configuration option.
Jul 22 11:11:48 ip-172-30-0-65.ec2.internal scylla[1630]:  [shard 0] seastar - Exiting on unhandled exception: std::runtime_error (Bad I/O Scheduler configuration)

roydahan on 22 Jul 2018

See c85fbd16cba35c94df81c14b63731fa689f190a8

    scylla_lib: drop support for m3 and c3 AWS instance types

C3 instances are no longer auto-configured.

glommer on 23 Jul 2018

👍1

Was this page helpful?

0 / 5 - 0 ratings

Related issues

Materialized view updates use incorrect schema to interpret writes after base table schema is altered

tgrabiec · 6Comments

Support multi-column restrictions in ALLOW FILTERING

psarna · 7Comments

collection indexing issue (bug)

LouayKamel · 6Comments

Bad performance on default CentOS/RHEL 7.0 kernel

avikivity · 4Comments

Provide Scylla Helm Charts to support Kubernetes installations

eyalgutkind · 3Comments