This should be our #1 priority until it is solved and we should document the solution here for future reference and be as open as possible about the solution with the community since it's causing massive downtime.
Click for server logs from this morning immediately after crash...
1/27 09:14 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:14 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:14 AM
Web push notifications to enabled!
11/27 09:14 AM Server starting...
11/27 09:14 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:14 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:17 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:17 AM npm start
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM npm start
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM npm start
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM npm start
11/27 09:17 AM npm start
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM npm start
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Server starting...
11/27 09:17 AM Server starting...
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM npm start
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM Server starting...
11/27 09:17 AM npm start
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM npm start
11/27 09:17 AM Server starting...
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM npm start
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM npm start
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM npm start
11/27 09:17 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:17 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:17 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:17 AM npm start
11/27 09:17 AM Server starting...
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Server starting...
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:17 AM npm start
11/27 09:17 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:17 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:17 AM
Web push notifications to enabled!
11/27 09:17 AM Server starting...
11/27 09:17 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:17 AM GraphQL server running at http://localhost:3001/api
11/27 09:18 AM npm start
11/27 09:18 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:18 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:18 AM
Web push notifications to enabled!
11/27 09:18 AM Server starting...
11/27 09:18 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:18 AM GraphQL server running at http://localhost:3001/api
11/27 09:18 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:18 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:18 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:18 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:18 AM npm start
11/27 09:18 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:18 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:18 AM
Web push notifications to enabled!
11/27 09:18 AM Server starting...
11/27 09:18 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:18 AM GraphQL server running at http://localhost:3001/api
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM npm start
11/27 09:19 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:19 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:19 AM
Web push notifications to enabled!
11/27 09:19 AM Server starting...
11/27 09:19 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:19 AM GraphQL server running at http://localhost:3001/api
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM undefined
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM undefined
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM undefined
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM undefined
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:19 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM { GraphQLError: Field "markDirectMessageNotificationsSeen" must not have a selection since type "Boolean" has no subfields.
at Object.Field (/home/nowuser/src/node_modules/graphql/validation/rules/ScalarLeafs.js:43:33)
at Object.enter (/home/nowuser/src/node_modules/graphql/language/visitor.js:297:29)
at Object.enter (/home/nowuser/src/node_modules/graphql/language/visitor.js:339:25)
at visit (/home/nowuser/src/node_modules/graphql/language/visitor.js:229:26)
at visitUsingRules (/home/nowuser/src/node_modules/graphql/validation/validate.js:76:22)
at Object.validate (/home/nowuser/src/node_modules/graphql/validation/validate.js:61:10)
at doRunQuery (/home/nowuser/src/node_modules/graphql-server-core/src/runQuery.ts:116:30)
at /home/nowuser/src/node_modules/graphql-server-core/src/runQuery.ts:59:39
at <anonymous>
message: 'Field "markDirectMessageNotificationsSeen" must not have a selection since type "Boolean" has no subfields.',
locations: [ { line: 2, column: 38 } ],
path: undefined }
11/27 09:20 AM undefined
11/27 09:20 AM undefined
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM { GraphQLError: Field "markAllNotificationsSeen" must not have a selection since type "Boolean" has no subfields.
at Object.Field (/home/nowuser/src/node_modules/graphql/validation/rules/ScalarLeafs.js:43:33)
at Object.enter (/home/nowuser/src/node_modules/graphql/language/visitor.js:297:29)
at Object.enter (/home/nowuser/src/node_modules/graphql/language/visitor.js:339:25)
at visit (/home/nowuser/src/node_modules/graphql/language/visitor.js:229:26)
at visitUsingRules (/home/nowuser/src/node_modules/graphql/validation/validate.js:76:22)
at Object.validate (/home/nowuser/src/node_modules/graphql/validation/validate.js:61:10)
at doRunQuery (/home/nowuser/src/node_modules/graphql-server-core/src/runQuery.ts:116:30)
at /home/nowuser/src/node_modules/graphql-server-core/src/runQuery.ts:59:39
at <anonymous>
message: 'Field "markAllNotificationsSeen" must not have a selection since type "Boolean" has no subfields.',
locations: [ { line: 2, column: 28 } ],
path: undefined }
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM undefined
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:20 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:21 AM npm start
11/27 09:21 AM
> [email protected] start /home/nowuser/src
> cross-env NODE_ENV=production node build-iris/main.js
11/27 09:21 AM Creating a pool connected to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015
11/27 09:21 AM
Web push notifications to enabled!
11/27 09:21 AM Server starting...
11/27 09:21 AM Web server running at http://localhost:3001 (server-side rendering enabled)
11/27 09:21 AM GraphQL server running at http://localhost:3001/api
11/27 09:22 AM undefined
11/27 09:22 AM undefined
11/27 09:22 AM undefined
11/27 09:22 AM undefined
11/27 09:22 AM undefined
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM undefined
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM undefined
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:22 AM undefined
11/27 09:22 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM undefined
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM undefined
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM undefined
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM undefined
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:24 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM undefined
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM undefined
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:25 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM undefined
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM undefined
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM undefined
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM undefined
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM undefined
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM undefined
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:26 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM Error: read ECONNRESET
at _errnoException (util.js:1024:11)
at TCP.onread (net.js:615:25)
11/27 09:27 AM npm ERR! code ELIFECYCLE
11/27 09:27 AM npm ERR! errno 1
11/27 09:27 AM npm ERR! [email protected] start: `cross-env NODE_ENV=production node build-iris/main.js`
11/27 09:27 AM npm ERR! Exit status 1
11/27 09:27 AM npm ERR!
11/27 09:27 AM npm ERR! Failed at the [email protected] start script.
11/27 09:27 AM npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11/27 09:27 AM
npm ERR! A complete log of this run can be found in:
11/27 09:27 AM npm ERR! /home/nowuser/.npm/_logs/2017-11-27T17_27_02_488Z-debug.log
11/27 09:27 AM Error: read ECONNRESET
at _errnoException (util.js:1024:11)
at TCP.onread (net.js:615:25)
11/27 09:27 AM npm ERR! code ELIFECYCLE
11/27 09:27 AM npm ERR! errno 1
11/27 09:27 AM npm ERR! [email protected] start: `cross-env NODE_ENV=production node build-iris/main.js`
11/27 09:27 AM npm ERR! Exit status 1
11/27 09:27 AM npm ERR!
11/27 09:27 AM npm ERR! Failed at the [email protected] start script.
11/27 09:27 AM npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11/27 09:27 AM
npm ERR! A complete log of this run can be found in:
11/27 09:27 AM npm ERR! /home/nowuser/.npm/_logs/2017-11-27T17_27_02_807Z-debug.log
11/27 09:27 AM Entering slow growth mode
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Error: read ECONNRESET
at _errnoException (util.js:1024:11)
at TCP.onread (net.js:615:25)
11/27 09:27 AM npm ERR! code ELIFECYCLE
11/27 09:27 AM npm ERR! errno 1
11/27 09:27 AM npm ERR! [email protected] start: `cross-env NODE_ENV=production node build-iris/main.js`
11/27 09:27 AM npm ERR! Exit status 1
11/27 09:27 AM npm ERR!
11/27 09:27 AM npm ERR! Failed at the [email protected] start script.
11/27 09:27 AM npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11/27 09:27 AM
npm ERR! A complete log of this run can be found in:
11/27 09:27 AM npm ERR! /home/nowuser/.npm/_logs/2017-11-27T17_27_03_999Z-debug.log
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Entering slow growth mode
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Error: read ECONNRESET
at _errnoException (util.js:1024:11)
at TCP.onread (net.js:615:25)
11/27 09:27 AM npm ERR! code ELIFECYCLE
11/27 09:27 AM npm ERR! errno 1
11/27 09:27 AM npm ERR! [email protected] start: `cross-env NODE_ENV=production node build-iris/main.js`
11/27 09:27 AM npm ERR! Exit status 1
11/27 09:27 AM npm ERR!
11/27 09:27 AM npm ERR! Failed at the [email protected] start script.
11/27 09:27 AM npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
11/27 09:27 AM
npm ERR! A complete log of this run can be found in:
11/27 09:27 AM npm ERR! /home/nowuser/.npm/_logs/2017-11-27T17_27_05_552Z-debug.log
11/27 09:27 AM Entering slow growth mode
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Entering slow growth mode
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Entering slow growth mode
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Exiting slow growth mode
11/27 09:27 AM Exiting slow growth mode
11/27 09:27 AM Exiting slow growth mode
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM undefined
11/27 09:27 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM undefined
11/27 09:27 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"msg":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s","message":"Failed to connect to ec2-54-153-126-86.us-west-1.compute.amazonaws.com:28015 in less than 20s.","isOperational":true}
11/27 09:27 AM Exiting slow growth mode
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM undefined
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM undefined
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:28 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:30 AM undefined
11/27 09:30 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:30 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:30 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:30 AM undefined
11/27 09:30 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:30 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:30 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM undefined
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:31 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM undefined
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM undefined
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM undefined
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM undefined
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM undefined
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:32 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:33 AM undefined
11/27 09:33 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:33 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:33 AM undefined
11/27 09:33 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:33 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:33 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM undefined
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM undefined
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM undefined
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM undefined
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM undefined
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM undefined
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:34 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM undefined
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:35 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM undefined
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM undefined
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM undefined
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM undefined
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:38 AM undefined
11/27 09:38 AM undefined
11/27 09:38 AM undefined
11/27 09:38 AM undefined
11/27 09:39 AM undefined
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM undefined
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM undefined
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM undefined
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:39 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:40 AM undefined
11/27 09:40 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:40 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:40 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:40 AM undefined
11/27 09:40 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:40 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:40 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM undefined
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:41 AM (node:82) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
11/27 09:42 AM undefined
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM undefined
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM undefined
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:42 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM undefined
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM undefined
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:43 AM undefined
11/27 09:43 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM undefined
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM undefined
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM undefined
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:45 AM undefined
11/27 09:46 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:46 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:46 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:46 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:47 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:47 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:48 AM undefined
11/27 09:48 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:48 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:48 AM undefined
11/27 09:48 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:48 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:48 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM undefined
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM undefined
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM undefined
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM undefined
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:49 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:50 AM undefined
11/27 09:50 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:50 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:50 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:50 AM undefined
11/27 09:50 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:50 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:50 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:51 AM undefined
11/27 09:51 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:51 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:51 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:51 AM undefined
11/27 09:51 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:51 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
11/27 09:51 AM WARNING: DraftEntity.get will be deprecated soon!
Please use "contentState.getEntity" instead.
I noticed a couple of GraphQL errors in there related to marking notifications seen. We're also seeing undefined show up a lot? Seemingly in relation to the composer.
FIX NOW
superbryntendo
All 36 comments
@mxstbr @brianlovin I just watched Sarah recreate the post that caused the crash this morning.
She noted that it didn't let her paste when she was creating it the first time - so she probably tried that multiple times.
Steps:
- Copy title from episode page on spec.fm => paste into title field
- Copy body text from episode page on spec.fm => paste into body field
- select top row, hit enter a few times to make room for embed
- Copy embed link from simplecast.fm => paste into embed field
- Publish
This time it worked, but it seems like the fact that it wouldn't let her paste before is a clue.
superbryntendo
on 27 Nov 2017
Investigating today, and the issue has to be the explore page. Here's why I think that is:
When you cold load the explore page we are doing a few things:
- Fetching top communities
- Fetching all of the curated communities, even if you're not viewing them
As a result of 1, our 'top communities' query is horribly unperformant. I wrote this ~6months ago at this point I'm guessing, and now that we have 1k+ communities, we're kicking off a stupid-silly number of db requests to figure out what the "top 20" are. I'm talking thousands of db requests. Yes, thousands.
As a result of 2, we're returning a fairly massive payload even though the user hasn't even requested to view any of the curated communities yet.
I'm going to dig in and do the following:
- statically store our 'top communities' somehow - and probably just go ahead and refactor it to be top 20 most active instead of top 20 by member count. This static list will be used to return the exact communities needed to the frontend
- make it so that the tabbed interface in explore only requests the curated communities it needs when a tab is clicked on
Just to paint a picture:
Loading the explore page locally takes >20 seconds. Insane.
brianlovin
on 29 Nov 2017
It’d be great to load the panels once the main view has loaded anyway. Want that experience to be fast as possible, right? No one will use them if they’re slow to load.
On Nov 29, 2017 at 1:45 PM,
Investigating today, and the issue has to be the explore page. Here's why I think that is:
When you cold load the explore page we are doing a few things:
Fetching top communities
Fetching all of the curated communities, even if you're not viewing them
As a result of 1, our 'top communities' query is horribly unperformant. I wrote this ~6months ago at this point I'm guessing, and now that we have 1k+ communities, we're kicking off a stupid-silly number of db requests to figure out what the "top 20" are. I'm talking thousands of db requests. Yes, thousands.
As a result of 2, we're returning a fairly massive payload even though the user hasn't even requested to view any of the curated communities yet.
I'm going to dig in and do the following:
statically store our 'top communities' somehow - and probably just go ahead and refactor it to be top 20 most active instead of top 20 by member count. This static list will be used to return the exact communities needed to the frontend
make it so that the tabbed interface in explore only requests the curated communities it needs when a tab is clicked on
Just to paint a picture:
Loading the explore page locally takes >20 seconds. Insane.—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub (https://github.com/withspectrum/spectrum/issues/2097#issuecomment-348006768), or mute the thread (https://github.com/notifications/unsubscribe-auth/AEstaEQTvNhCUVlhOx-a8ZH-0aUAvID-ks5s7dBwgaJpZM4QsHMJ).
superbryntendo
on 29 Nov 2017
I can look into preloading them if a user hovers over the tab or something to give the network request a head start. Loading 10 communities or something will be quite fast anyways
brianlovin
on 29 Nov 2017
Yeah we can preload when a user hovers, Apollo has some primitives to do that.
What about making the top 20 more like a leaderboard? "Here are the top 20 most active communities of the week" We have that data somewhere anyway haha, we could probably store it at night when we compute the WAC etc?
mxstbr
on 29 Nov 2017
Yup, I'm on it!
brianlovin
on 29 Nov 2017
@mxstbr thinking it will work like this:
- create a table called
curatedContentwith the model:
{
id: ID
type: string
data: Array<any>
}
- we just manually query against that table by
type- e.g. a type might be 'top communities by member count' or 'design communities' - the goal is having it abstract enough to eventually curate anything - users, threads, watercoolers, whatever
Additionally:
- use the coreMetrics cron job to just daily update the 'top communities' with the list of monthly actives or something?
- pre-load the curated community collections on tab hover
- index the 'communities' table by
slugfor faster lookups all around
brianlovin
on 29 Nov 2017
Sure, sounds good.
use the coreMetrics cron job to just daily update the 'top communities' with the list of monthly actives or something?
I don't think monthly actives will be enough for a while, I'd make it the monthly actives + some others we want to be active? (e.g. gatsby, next, whatever)
index the 'communities' table by slug for faster lookups all around
Just look them up by ID........ :wink: The only time we look them up by slugs is when you visit a community page directly, otherwise it's always by ID.
mxstbr
on 29 Nov 2017
Also, I'm 99% positive the coreMetrics cron is crashing the server every night at 1am when it runs, because it does the same data-hungry query to figure out the top communities (in order for us to determine the monthly actives). . ..
I think the eventual solution to this @mxstbr will be to have a read-only slave db in the future that we perform heavy queries against (e.g. daily digests, core metrics, admin dashboard)
brianlovin
on 29 Nov 2017
Just look them up by ID........ 😉
We are already doing a really dumb getCommunitiesBySlug lookup to figure out which community to load when a user lands on spectrum.chat/:slug so...might as well :P
brianlovin
on 29 Nov 2017
Did an early push with better fetching from the curatedContent table, aliasing that now. I have followup tasks to make it more performant and update the topCommunities list from our core metrics somehow
brianlovin
on 30 Nov 2017
@mxstbr not sure if this could be it, but could the web-push-notifications logic be triggering a few thousand hits to the db every time a thread is published in a popular community?
brianlovin
on 30 Nov 2017
Hmm, maybe. Let me take a look at that.
mxstbr
on 30 Nov 2017
Nope, that runs on an index and we don't have that many web push subscriptions, so that's not it. (~500)
mxstbr
on 30 Nov 2017
@brianlovin now, the slowest query is still on the explore page and it's getting all the member counts for all of those communities:
That is quite expensive for a single community, but for the amount of communities we load on the explore page it's obscene. Didn't we want to stop showing those anyway? Let's do that? 😅
mxstbr
on 30 Nov 2017
Will do!
brianlovin
on 30 Nov 2017
Kk explore page is trimmed down in #2118
Going to do some more investigating
brianlovin
on 30 Nov 2017
Maybe it is watercoolers, but more specifically, any thread with a high message count.
A clean refresh on the netlify watercooler thread directly runs 75 queries for me. Some of the responses are quite big (170k is the biggest to return all messages)
A clean refresh on my inbox where the netlify watercooler is the first thread in the inbox loads 57 queries. A few are big, several of them are >100ms response time.
brianlovin
on 30 Nov 2017
Yep, that's what I mean with #2109, not talking only about the watercooler :blush:
mxstbr
on 30 Nov 2017
One thing that is hurting us in terms of request size is getting user permissions in communities. For every message we are getting that user's permission in the community, which is a bit crazy. See:
This could have been introduced a few weeks ago when I added the 'admin' badge that shows up next to a person's username with their messages.
One possible solution to this is to denormalize admin ids to the community model, and then use that array to determine isAdmin in the messages components
brianlovin
on 30 Nov 2017
@mxstbr this one change took a response size from >100kb to ~20kb: https://github.com/withspectrum/spectrum/pull/2120/commits/025bb21dcb970a06ed86b5972312e9304cac4875
Looking for more opportunities to do this now...
brianlovin
on 30 Nov 2017
On user profiles we're requesting a user 40+ times:
brianlovin
on 30 Nov 2017
are you recording this for future work or do you think this is part of the problem?
do we think that it's request size or frequency causing the issue?
superbryntendo
on 30 Nov 2017
I'm recording this for future work, trying to find areas where we're making superfluous requests
brianlovin
on 30 Nov 2017
👍1
I assumed it was an infinite loop causing the issue not large responses
superbryntendo
on 30 Nov 2017
I don't know what's causing it. At this point I'm trying to find anything that could be slamming our database, infinite loop or otherwise :/
brianlovin
on 30 Nov 2017
Two more things we're doing which are kind of annoying to sort out, but are definitely slamming the db:
every thread gets the
usersCommunitiesandusersChannelspermissions for every participant. This happens even if you're viewing a community profile where none of that information is exposed or used in any way. The reason we have this is because we wanted apollo to read threads from the cache, and in the thread detail we do want that information, so we include it everywhere.less of a big deal, but every community fetches the
isProfield which hits therecurringPaymentstable - none of these are big requests necessarily, or time expensive, but they happen everywhere - including on thread cards
brianlovin
on 30 Nov 2017
On user profiles we're requesting a user 40+ times:
Sounds like a missing loader?
mxstbr
on 30 Nov 2017
Sounds like a missing loader?
Found it
brianlovin
on 30 Nov 2017
Loading user profiles while faster is still putting a lot of data into memory. While I got the query for 'all threads where the user is a participant' down to ~400ms (slow, I know, but better than 10s+), it is still loading 14k+ records from the usersChannels table....working on this now
brianlovin
on 1 Dec 2017
Okay I've spent all day digging through this, a bit burnt out now.
See #2120 for a bunch of quick wins, needs your eye @mxstbr
More notes:
- using the
.distinct()call on theusersCommunititestable is ~250x slower than if we filtered the incoming data (when hitting theuserIdandCommunityIdcompound index) - removing it bloats the size. - our
orderBy('reputation')is ~250x slower than returning users randomly...not sure the best way to handle that, or if it's a big deal (1ms vs 250ms in the query) - not a huge query overall, but gets hit every time you view community members. - paginating thread messages ( #2109 ) is still going to be a massive win, although I have no clue how to handle this from a user experience perspective yet - do we only load the latest N messages? How do we provide that context in the UI that you're viewing a subset of the conversation that doesn't start from the first message? Is this a shitty experience for people who leave messages early in a thread? I think the more ideal experience here actually is to load the first N messages in a thread, and as the user scrolls we lazy load in the next batch with some kind of loading indicator...but then this gets hard as fuck when we do the
forceScrollToBottomwhen loading a thread where you're a participant. FUCK! - I spent several hours trying to make user profiles thread queries more performant. It's fucking hard. Got some help from Kelly, but I have no clue how to make this better. I threw in some
console.times in the code to help me see what's going on in the backend...it's still faster than it used to be, but ~1s for signed-in users because we have to do so many more permission checks against private channels. - there is an incredibly bad bug with notifications pagination on the notifications view. @mxstbr see if you can replicate this, but basically if I scroll down to the bottom of my notifications view it kicks off some kind of infinite loading/request state...
- I also discovered why sometimes shit paginates, and sometimes it doesn't! i fixed this on user profiles, but still need to double check on community/channel views. Basically if we do a
limit()call anywhere in the db before wefilter()results, we could potentially be returning a number of records less than thefirstargument. I can reproduce this pretty consistently when viewing my notifications view - we are limiting the results to 10, then filtering outdirectMessageThreadnotifications, which means the client is getting < 10 records, which means thehasNextPagegets set to false in the resolver!! You can see this clearly happening ingetNotificationsByUseriniris/models/notification.js:5 - we are also slamming the database with a ton of small requests for things like
usersPermissionInCommunityandusersReputationInCommunitywhen that data is never or rarely used. For example: when you load a thread with 400 messages, each of those messages is hitting theusersCommunititestable to get that user's permissions in the community in order to render theadminbadge in the client. I mentioned this elsewhere, but we should consider denormalizing admin ids for communities... - and finally: I'm noticing a lot of inconsistencies with the
rethinkdb-inspectorresults and running queries manually inlocalhost:8080- sometimes thequeries-by-timewill tell me a query took 200ms+, but running it in the rethink console I get the results in 2ms...differences like that make some of this perf work confusing because I can't tell if there's actually a problem there - one bug where user profile threads can't paginate if the channels list is super long
brianlovin
on 1 Dec 2017
And finally: @mxstbr, the Zeit team invited us to a slack channel in their core team for faster support. You can catch up on our convo in there - you should have gotten an invite to [email protected]. The one actionable thing I did was set our pool to min: 5, max: 200 based on Guillermo's advice. No more crashes since then...fwiw.
Otherwise the main conversation in there was around caching and how we should think about caching certain views for non-authed users with a maxAge at a reasonable amount, or just lazy-reconcile messages on the client so those are always fresh
brianlovin
on 1 Dec 2017
I'm noticing a lot of inconsistencies with the rethinkdb-inspector results and running queries manually in localhost:8080
This is 100% expected. From the README of the module:
“Note: The time it takes for a query to complete is very dependent on the system you're running on. Take the generated times with a grain of salt and only compare them between each other, see them as a ranking of queries, never compare the time between different machines or runs or tools.”
rethinkdb-inspector is end-to-end, it tracks the time from when .run() is called until the result comes back into .then(). (it does so by monkey-patching .run() under-the-hood, similar to what you did with console.time and console.timeEnd in #2120) localhost:8080 only shows the time it took the db to compute the response, not how long it took to send the query and then the response back.
For example, even though rethinkdb might only take 2ms to compute the response, because it's such a massive ton of data it still takes 200ms until the data is sent back, .then() is called and our server can do anything, so that's bad.
It's meant to be helpful for what we're trying to do (figure out what's the slowest part of our backend), not as a replacement for running the query profiler. It's not an accurate judgement of the time it took to complete, it's meant as a judgement of a ranking of the slowest queries. Ignore the exact time, that'll never be accurate, and look at the ranking as the source of truth.
mxstbr
on 1 Dec 2017
using the .distinct() call on the usersCommunitites table is ~250x slower than if we filtered the incoming data (when hitting the userIdandCommunityId compound index) - removing it bloats the size.
I know, that's why I said we should filter the inputs rather than in the database or the result. I can tackle that today.
we are also slamming the database with a ton of small requests for things like usersPermissionInCommunity and usersReputationInCommunity when that data is never or rarely used.
Don't we have loaders for those? Then we shouldn't be "slamming the db" with those queries, there should only be one or two batched ones on every request.
mxstbr
on 1 Dec 2017
Adding related threads here so we can track centrally:
- [ ] [DB connections crashing](https://github.com/withspectrum/spectrum/issues/1969)
- [ ] [500 error when sending message](https://github.com/withspectrum/spectrum/issues/1395)
- [ ] [Server 502 issues](https://github.com/withspectrum/spectrum/issues/1768)
superbryntendo
on 4 Dec 2017
Going to close this as we are no longer going time 23x per day. We have other open perf issues to work through from here on out, but I'd call this pretty stable.
brianlovin
on 8 Dec 2017
👍1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
zefexdeveloper
·
5Comments
brianlovin
·
3Comments
atlx
·
5Comments
brianlovin
·
5Comments
mxstbr
·
5Comments