Failed to run when use redis and elasticsearch in AWS

Version 2.5.8

I tried to run conductor in my computer before deploy to k8s So I ran conductor that was setup the connection to connect to elasticsearch and redis, both inside in aws

The result I got is not what I expected to be same as running conductor with dynomite and elasticsearch in local host by using docker-compose (So conductor works in localhost)

I have 1 elasticsearch setup in aws

and 1 redis with 1 replica in aws

config.properties

# Servers.
conductor.jetty.server.enabled=true
conductor.grpc.server.enabled=false

# Database persistence model.  Possible values are memory, redis, and dynomite.
# If ommitted, the persistence used is memory
#
# memory : The data is stored in memory and lost when the server dies.  Useful for testing or demo
# redis : non-Dynomite based redis instance
# dynomite : Dynomite cluster.  Use this for HA configuration.

db=redis

# Dynomite Cluster details.
# format is host:port:rack separated by semicolon
workflow.dynomite.cluster.hosts=redishostin.aws.com:6379:ap-southeast-1a;

# Dynomite cluster name
workflow.dynomite.connection.maxConnsPerHost=1

# Namespace for the keys stored in Dynomite/Redis
workflow.namespace.prefix=conductor

# Namespace prefix for the dyno queues
workflow.namespace.queue.prefix=conductor_queues

# No. of threads allocated to dyno-queues (optional)
queues.dynomite.threads=10

# Non-quorum port used to connect to local redis.  Used by dyno-queues.
# When using redis directly, set this to the same port as redis server
# For Dynomite, this is 22122 by default or the local redis-server port used by Dynomite.
queues.dynomite.nonQuorum.port=6379

# Elastic search instance type. Possible values are memory and external.
# If not specified, the instance type will be embedded in memory

##Elasticsearch major release version.
workflow.elasticsearch.version=5

# memory: The instance is created in memory and lost when the server dies. Useful for development and testing.
# external: Elastic search instance runs outside of the server. Data is persisted and does not get lost when
#           the server dies. Useful for more stable environments like staging or production.
workflow.elasticsearch.instanceType=external

workflow.elasticsearch.cluster.health.color=yellow

# Transport address to elasticsearch
workflow.elasticsearch.url=elasticsearch.ap-southeast-1.es.amazonaws.com:443
# Name of the elasticsearch cluster
workflow.elasticsearch.index.name=conductor

# Additional modules (optional)
# conductor.additional.modules=class_extending_com.google.inject.AbstractModule

# Load sample kitchen sink workflow
loadSample=true

This is an error message that always show and don’t know how to solve it because the message is quite unclear

Error in custom provider, java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: 0

These are errors I got error.log

[kishorebanala]

Hey @kishorekasi @smukil , can you help with this? We’re wondering if this is related to Dynomite configuration.

[github-actions[bot]]

This issue was closed, because it has been stalled for 7 days with no activity.