Ben Coughlan's questions

I'm in IP tables hell, for the first time in ten years!

# Generated by iptables-save v1.6.0 on Fri Jan 10 16:36:24 2020
*nat :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :OUTPUT ACCEPT [6:371] :POSTROUTING ACCEPT [6:371]
-A PREROUTING -p tcp -m tcp --dport 3306 -j DNAT --to-destination 172.25.25.50:3306
-A PREROUTING -p tcp -m tcp --dport 3307 -j DNAT --to-destination 172.25.25.226:3306
-A POSTROUTING -d 172.25.25.50/32 -p tcp -m tcp --dport 3306 -j SNAT --to-source 10.128.128.52
-A POSTROUTING -d 172.25.25.226/32 -p tcp -m tcp --dport 3306 -j SNAT --to-source 10.128.128.52 COMMIT
# Completed on Fri Jan 10 16:36:24 2020

Basically I have 2 independent mysql server instances on the end of the line.

Server 1 - 172.25.25.50:3306 can be reached successfully.

Server 2 - 172.25.25.226:3307 cannot be hit at all.

The source is the same for both, it's an LB - 10.128.128.52, which is why Server 1 and Server 2 are using different ports. port 3306/3307 are open on the LB and the machine, I think.

Forwarding is turned on, both on the server OS and the instance settings..

    root@art-proxy1-us:/home/ben# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination
DNAT       tcp  --  anywhere             anywhere             tcp dpt:mysql to:172.25.25.50:3306
DNAT       tcp  --  anywhere             anywhere             tcp dpt:3307 to:172.25.25.226:3306

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
SNAT       tcp  --  anywhere             172.25.25.50        tcp dpt:mysql to:10.128.128.52
SNAT       tcp  --  anywhere             172.25.25.226       tcp dpt:mysql to:10.128.128.52

HALP! :D

The company I work for is currently going through an AWS migration, and for 99% of services, their commodity hardware does the job just fine.

Except for the production Database, we currently sit at 60,000 IOPS just to keep up with requests, and it's due to see much more action this year.

We've looked at using enterprise SSD's on EC2, but the IOPS hard limit is 20,000, which is pretty terrible, considering I can get a 240GB SSD that performs at 80,000 IOPS for about €200. http://www.techradar.com/reviews/pc-mac/pc-components/storage/disk-drives-hdd-ssd/intel-ssd-520-series-240gb-1060850/review

Any idea's how I can get past this limit? Is a cluster/RAID of ebs volumes possible?

Thanks, Ben

I'm trying to setup snapmirror between two cluster mode netapp filers.

However, one is in the US, the other is in China.

We have two different unix groups setup here, as a security measure.

i.e. we have group users.usa in the USA, and users.china in China.

users.usa cannot view users.china files, and vice versa, and nobody in china can be a member of users.usa/vice versa.

So can I snapmirror the users.usa data to china, and change the unix group of the files to users.china, i.e. is there a netapp option for that?

Also, by doing this, would I completely screw up the compression/snapmirror comparison algorithm, as the files would technically be different, no?

Thanks for this, we're rocking onTap 8.3 on both filers.

Ben