Start a Conversation

Unsolved

This post is more than 5 years old

6218

September 15th, 2009 16:00

Centera connection pooling

Hi

We are in the process of developing custom components to store images to Centera.  In related to this, i am looking for sample code or approach on how do we implement connection pooling - like the one to connect to DB.  This is because, we need to process Million's of images per day and I dont want to open and close connections each time.  What is the industry best practice in using Centera?  Any help or pointer on this would be highly appreciated.

Thanks

Sugu, PMP

212 Posts

September 15th, 2009 17:00

Hi Sugu,

You might want to post this question in the Centera developer community -

Thanks,

Aashish

790 Posts

September 17th, 2009 08:00

This question has been moved to the EMC Centera Developer community

409 Posts

September 17th, 2009 09:00

Sugu

You can download from the EDN Centera section our best practises but in summary we recommend that you only open one pool connection and then use that pool connection for all your IO threads.

Your application can have up to 20 IO threads per access node on the centera although remember this number is shared between all applications that may be using the centera cluster

1 Rookie

 • 

3 Posts

September 17th, 2009 13:00

Thanks Paul.  This means Centera SDK or XAM APIs do not create or maintain any pool of connections.. instead its application teams responsibilities to create 10 or whatever number of connections upfront, pool it, serve it and close it.  Is my understanding correct?

Any update on how long the connection will be open from Centra side.  Like once I open a connection, will it be alive till I close the connection or there will be some timout period associated with each connections.

Thanks in advance

Sugu

409 Posts

September 17th, 2009 14:00

under the covers the SDK will open up a number of socket connections which it will use when one of your threads does an IO.  The application creates the threads and typically uses that pool of threads to do IOs.  As your threads performs a write or read SDK operation the SDK will use an available socket to talk to the cluster.

The pool connection can be kept open for as long as your application is up.  There is no need to close and reopen.

1 Rookie

 • 

3 Posts

September 17th, 2009 18:00

Thanks Paul for your quick response.  This answers my question, but I do have one last question.  How do you handle concurrent reads or writes?  For example, in my application there will be 15 (you can pick a number) concurrent users who can try to read/write images from/to Centera.  In such case, I need to write my own connection pooling logic - like start of the application I need to create 15 connection, right...  We are planning to use XAM and our application is going to be in Java.

409 Posts

September 29th, 2009 00:00

I'm assuming your application will will access the Centera on behalf of your users regardless of the number of users.  In that case your application would open one pool/xsystem connection and your IO thread pool which satisfies user requests, would use that one connection.

 

1 Rookie

 • 

1 Message

December 2nd, 2024 15:58

Hi everyone,

Is there someone who knows where I can get the Centera SDK?

Thanks 

No Events found!

Top