Ignite AWS S3 Discovery Issue

classic Classic list List threaded Threaded
4 messages Options
Rout, Biswajeet Rout, Biswajeet
Reply | Threaded
Open this post in threaded view
|

Ignite AWS S3 Discovery Issue

Hi,

I have used the S3 discovery mechanism to discovers the node in the ignite cluster.
I have used two different buckets for two different instance of my application. Where as I can see irrespective of bucket, the nodes are discovering each other and forming clusters.

Is there any configuration except my config, where the servers under one bucket will discover watch other?

image.png
I am passing two different names for ${S3_BUCKET_NAME} dynamically for two different applications.

Regards,


Biswajeet Rout


Dtix-DELPHI


O 181 361 7630
M 970 334 9977

      

Evgeniy Rudenko Evgeniy Rudenko
Reply | Threaded
Open this post in threaded view
|

Re: Ignite AWS S3 Discovery Issue

Hi Biswajee,

This is configured only in the section that you sent. Unless you redefine this in your java code.

Are you sure that you actually set different names for ${S3_BUCKET_NAME}? Can you send logs to check current behaviour?

On Mon, Oct 21, 2019 at 1:17 PM Rout, Biswajeet <[hidden email]> wrote:
Hi,

I have used the S3 discovery mechanism to discovers the node in the ignite cluster.
I have used two different buckets for two different instance of my application. Where as I can see irrespective of bucket, the nodes are discovering each other and forming clusters.

Is there any configuration except my config, where the servers under one bucket will discover watch other?

image.png
I am passing two different names for ${S3_BUCKET_NAME} dynamically for two different applications.

Regards,


Biswajeet Rout


Dtix-DELPHI


O 181 361 7630
M 970 334 9977

      



--
Best regards,
Evgeniy
Rout, Biswajeet Rout, Biswajeet
Reply | Threaded
Open this post in threaded view
|

Re: [E] Re: Ignite AWS S3 Discovery Issue

Hi,

Actually I see a trace of exception in my ignite log. it says "Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The provided token has expired". Is it related to some issue in S3 bucket?

image.png

Regards,


Biswajeet Rout


Dtix-DELPHI


O 181 361 7630
M 970 334 9977

      



On Mon, Oct 21, 2019 at 6:17 PM Evgeniy Rudenko <[hidden email]> wrote:
Hi Biswajee,

This is configured only in the section that you sent. Unless you redefine this in your java code.

Are you sure that you actually set different names for ${S3_BUCKET_NAME}? Can you send logs to check current behaviour?

On Mon, Oct 21, 2019 at 1:17 PM Rout, Biswajeet <[hidden email]> wrote:
Hi,

I have used the S3 discovery mechanism to discovers the node in the ignite cluster.
I have used two different buckets for two different instance of my application. Where as I can see irrespective of bucket, the nodes are discovering each other and forming clusters.

Is there any configuration except my config, where the servers under one bucket will discover watch other?

image.png
I am passing two different names for ${S3_BUCKET_NAME} dynamically for two different applications.

Regards,


Biswajeet Rout


Dtix-DELPHI


O 181 361 7630
M 970 334 9977

      



--
Best regards,
Evgeniy
dmagda dmagda
Reply | Threaded
Open this post in threaded view
|

Re: [E] Re: Ignite AWS S3 Discovery Issue

This sounds like an AWS issue. Please consult with their troubleshooting guide and let us know if the issue is resolved or persists.

-
Denis


On Tue, Oct 22, 2019 at 12:31 AM Rout, Biswajeet <[hidden email]> wrote:
Hi,

Actually I see a trace of exception in my ignite log. it says "Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: The provided token has expired". Is it related to some issue in S3 bucket?

image.png

Regards,


Biswajeet Rout


Dtix-DELPHI


O 181 361 7630
M 970 334 9977

      



On Mon, Oct 21, 2019 at 6:17 PM Evgeniy Rudenko <[hidden email]> wrote:
Hi Biswajee,

This is configured only in the section that you sent. Unless you redefine this in your java code.

Are you sure that you actually set different names for ${S3_BUCKET_NAME}? Can you send logs to check current behaviour?

On Mon, Oct 21, 2019 at 1:17 PM Rout, Biswajeet <[hidden email]> wrote:
Hi,

I have used the S3 discovery mechanism to discovers the node in the ignite cluster.
I have used two different buckets for two different instance of my application. Where as I can see irrespective of bucket, the nodes are discovering each other and forming clusters.

Is there any configuration except my config, where the servers under one bucket will discover watch other?

image.png
I am passing two different names for ${S3_BUCKET_NAME} dynamically for two different applications.

Regards,


Biswajeet Rout


Dtix-DELPHI


O 181 361 7630
M 970 334 9977

      



--
Best regards,
Evgeniy