10.216.218.73=dc1:rac1
10.31.2.31=dc2:rac1
default=dc1:rac1
create keyspace helloworld with replication ={'class': 'NetworkTopologyStrategy', 'dc1': 1, 'dc2',1};
| Port | Description |
|---|---|
| Public Facing Ports | |
| 22 | SSH port. |
| 8888 | OpsCenter website port. |
| Cassandra Inter-node Ports | |
| 1024+ | JMX reconnection/loopback ports. See description for port 7199. |
| 7000 | Cassandra inter-node cluster communication. |
| 7199 | Cassandra JMX monitoring port. After the initial handshake, the JMX protocol requires that the client reconnects on a randomly chosen port (1024+). |
| 9160 | Cassandra client port (Thrift). |
| OpsCenter ports | |
| 61620 | OpsCenter monitoring port. The opscenterd daemon listens on this port for TCP traffic coming from the agent. |
| 61621 | OpsCenter agent port. The agents listen on this port for SSL traffic initiated by OpsCenter. |
java version "1.6.0_38"
Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
cassandra -version
cqlsh --versionWe want to save the data in the ephemeral drive. The mount point we created earlier is /vol
nodetool -h localhost -p 7199 ringReboot and check if it's running by running "netstat -tupln"
cluster_name: my_clusterStart Cassandra. If you face any problems starting it, delete all the files in commitlog_directory and data_file_directories.
initial_token: 0
umount /mntNow edit /etc/cassandra/cassandra.yaml.
vi /etc/fstab
uncomment "/dev/xvdb /vol xfs noatime 0 0" and remove entries that are using /dev/xvdb if appropriate
mkfs.xfs -f /dev/xvdb
mount /vol
mkdir /vol/cassandra
mkdir /vol/cassandra/commitlog
mkdir /vol/cassandra/data
mkdir /vol/cassandra/saved_caches
chown cassandra:cassandra -R /vol/cassandra
- seeds: "10.31.2.31,10.216.218.73"
listen_address: 10.31.2.31For the second node,
rpc_address: 10.31.2.31
listen_address: 10.216.218.73
rpc_address: 10.216.218.73
#! /usr/bin/pythonChange it to an executable.
import sys
if (len(sys.argv) > 1):
num=int(sys.argv[1])
else:
num=int(raw_input("How many nodes are in your cluster? "))
for i in range(0, num):
print 'node %d: %d' % (i, (i*(2**127)/num))
chmod 777 token_generator.pyExecute the program with the number of nodes as the first argument. In our case, it's 2.
./token_generator.py 2The output should be similar to the following
node 0: 0Put 85070591730234615865843651857942052864 as the initial token for the second node.
node 1: 85070591730234615865843651857942052864
initial_token: '85070591730234615865843651857942052864'If you get DatabaseDescriptor.java (line 509) Fatal configuration error, you are probably using Cassandra 1.2.x.
nodetool status
service cassandra startCheck the status:
create keyspace helloworld with replication ={'class': 'NetworkTopologyStrategy', 'dc1': 1, 'dc2',1};
create table activity (
activity_key int,
activity_time timeuuid,
activity_type varint,
primary key (activity_key, activity_time)
)
with clustering order by (event_time desc);
cqlsh 10.216.218.73 -f test.cqlCheck to see if the keyspace "helloworld" exists:
cqlsh 10.216.218.73
describe keyspaces;
telnet 10.31.2.31 9160
proxy.balance = "hash"
proxy.server = ( "" =>
(
( "host" => "10.204.199.85",
"port" => 80
),
( "host" => "10.202.111.140",
"port" => 80
)
)
)
service lighttpd restart
netstat -ntulp
sudo apt-get install -y mysql-serverStop the local MySQL server. We won't be using it.
sudo /etc/init.d/mysql stopConnect to your RDS instance
mysql -h {rds_public_address} -P 3306 -u{username} -p{password}Do NOT use the following form. You will get a access denied.
mysql -u{username} -p{password} -h {rds_public_address} -P 3306
| Server Name: | email-smtp.us-east-1.amazonaws.com |
| Port: | 25, 465 or 587 |
| Use Transport Layer Security (TLS): | Yes |
| Authentication: | Your SMTP credentials - see below. |
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@This can happen when you are associating your Elastic IP to another instance.
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
aa:c3:4d:d2:db:64:17:f0:b3:9c:77:d7:47:2f:31:ab.
Please contact your system administrator.
rm ~/.ssh/known_hosts
ssh -i {your key} ubuntu@{your_ec2_public_address}sudo apt-get update
nginx -vIf this is not the latest version, do the following:
deb http://nginx.org/packages/ubuntu/ precise nginxsudo apt-get update
deb-src http://nginx.org/packages/ubuntu/ precise nginx
W: GPG error: http://nginx.org precise Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ABF5BD827BD9BF62Add the public key:
dpkg: error processing /var/cache/apt/archives/nginx_1.2.6-1~precise_amd64.deb (--unpack):
trying to overwrite '/etc/logrotate.d/nginx', which is also in package nginx-common 1.1.19-1ubuntu0.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/nginx_1.2.6-1~precise_amd64.deb
update-rc.d nginx defaults
ifconfig eth0 | grep inet | awk '{ print $2 }'
cp /etc/nginx/sites-available/default /etc/nginx/sites-available/{domain}Put the following into the file:
proxy_next_upstream error timeout invalid_header http_500;Check out proxy_read_timeout as well.
proxy_connect_timeout 1;
rm /etc/nginx/sites-enabled/defaultEnable the configuration by symbolic link to sites-enabled.
sudo ln -s /etc/nginx/sites-available/{domain} /etc/nginx/sites-enabled/{domain}If Nginx doesn't seem to pick up on the configuration, make sure /etc/nginx/nginx.conf has the following within the http block:
include /etc/nginx/sites-enabled/*;Restart the server.
service nginx restartTo deploy code without service interruption, read Nginx - How to deploy code without service disruption.
# /etc/nginx/sites-available/backendTo update backend1.example.com, mark it as down,
upstream backend {
server backend1.example.com:8080;
server backend2.example.com:8080;
}
# /etc/nginx/sites-available/backend
upstream backend {
server backend1.example.com:8080 down;
server backend2.example.com:8080;
}
upstream backend {
server backend1.example.com:8080;
server backend2.example.com:8080 down;
}
Ex. ssh -i {key} ubuntu@{ec2-address}.compute-1.amazonaws.comsudo apt-get update
Ex. sudo n 0.8.18If the version is not installed, the n cmd will automatically install the version for you. If the version is installed, then it will simply switch to that version.
/usr/local/lib/
public class VideoController {
@RequestMapping(value="/hello", method = RequestMethod.GET)
public ModelAndView sayHello() {
return new ModelAndView("hello");
}
}
Do not create additional name serve (NS) or start of authority (SOA) records in the Route 53 hosted zone, or delete the existing records.Click on Create Record Set.
Do not add a start of authority (SOA) record to the zone file for the parent domain. Because the subdomain will use Route 53, the DNS service for the parent domain is not the authority for the subdomain.
If your DNS service automatically added an SOA record for the subdomain, delete the record for the subdomain. However, do not delete the SOA record for the parent domain.Wait until the DNS is progagate.
define('DB_NAME', 'database_name_here');
/** MySQL database username */
define('DB_USER', 'username_here');
/** MySQL database password */
define('DB_PASSWORD', 'password_here');
/** MySQL hostname */
define('DB_HOST', 'localhost');
/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');
/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');
define('AUTH_KEY', 'put your unique phrase here');
define('SECURE_AUTH_KEY', 'put your unique phrase here');
define('LOGGED_IN_KEY', 'put your unique phrase here');
define('NONCE_KEY', 'put your unique phrase here');
define('AUTH_SALT', 'put your unique phrase here');
define('SECURE_AUTH_SALT', 'put your unique phrase here');
define('LOGGED_IN_SALT', 'put your unique phrase here');
define('NONCE_SALT', 'put your unique phrase here');
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Order allow,deny
allow from all
| For this parameter... | ...Do this: |
|---|---|
| License Model | Select the default, General-Public-License, to use the general license agreement for MySQL. |
| DB Engine Version | Select 5.5.20 to use the default version of MySQL. Note that RDS supports additional versions of MySQL. |
| DB Instance Class | Select db.m1.small to select a configuration that equates to 1.7 GB memory, 1 ECU (1 virtual core with 1 ECU), 64-bit platform, and moderate I/O capacity. for more information about the capacity for all the DB Instance class options, see Amazon Relational Database Service Features. |
| Multi-AZ Deployment | Select No to not request that your database be made available in multiple availability zones. For more information about multiple availability zones, see the RDS documentation. |
| Auto Minor Version Upgrade | Select Yes to enable your DB Instance to receive minor DB Engine version upgrades automatically when they become available. |
| Allocated Storage | Type 5 to allocate 5 GB of storage for your database. In some cases, allocating a higher amount of storage for your DB Instance than the size of your database can improve I/O performance. For more information about storage allocation, see Amazon Relational Database Service Features. |
| Use Provisioned IOPS | Leave the check box unselected. This option turns on Provisioned IOPS (I/O operations per second), a high-performance storage option in RDS that is optimized for I/O-intensive, transactional (OLTP) database workloads. For more information about high performance storage, see Provisioned IOPS. |
| DB Instance Identifier | Type a name for the DB Instance that is unique for your account in the region you selected. You may chose to add some intelligence to the name such as including the region and DB Engine you selected, for example west2-mysql-instance1. |
| Master User Name | Type a name using alphanumeric characters that you will use as the master user name to log on to your DB Instance with all database privileges. |
| Master User Password | Type a password that contains from 8 to 16 printable ASCII characters (excluding /,", and @) for your master user password. |
Type ImageID Name Owner State Accessibility ProductCodes Architecture ImageType KernelId RamdiskId Platform RootDeviceType VirtualizationType HypervisorThe highlighted text shows the root device type.
IMAGE ami-a29943cb 099720109477/ubuntu/images/ebs/ubuntu-precise-12.04-amd64-server-20120424 099720109477 available public x86_64 machine aki-825ea7eb ebs paravirtual xen
| Characteristic | Amazon EBS-Backed | Amazon instance store-backed |
|---|---|---|
Boot Time
|
Usually less than 1 minute
|
Usually less than 5 minutes
|
Size Limit
|
1 TiB
|
10 GiB
|
Root Device Volume
|
Amazon EBS volume
|
Instance store volume
|
Data Persistence
|
Data on Amazon EBS volumes persists after instance termination; you can also attach instance store volumes that don't persist after instance termination
|
Data on instance store volumes persists only during the life of the instance; you can also attach Amazon EBS volumes that persist after instance termination
|
Upgrading
|
The instance type, kernel, RAM disk, and user data can be changed while the instance is stopped.
|
Instance attributes are fixed for the life of an instance
|
Charges
|
Instance usage, Amazon EBS volume usage, and Amazon EBS snapshot charges for AMI storage
|
Instance usage and Amazon S3 charges for AMI storage
|
AMI Creation/Bundling
|
Uses a single command/call
|
Requires installation and use of AMI tools
|
Stopped State
|
Can be placed in stopped state where instance is not running, but the instance is persisted in Amazon EBS
|
Cannot be in stopped state; instances are running or terminated
|
