the paxos in chubby [closed] - paxos

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
In chubby the process of each log that write to db is one instance of the paxos process, and this instance may have many proposers, so it will have a master selected process.
why it has many proposers?

Having a single leader (aka a "Distinguished Proposer") is an optimization for Paxos. The whole point of Paxos is to decide a value when there are multiple proposers proposing different things.
The whole point of having multiple proposers is in case the "Distinguished Proposer" fails; something has to pick up that new role. Paxos, when it decides a value, implicitly decides between proposers.
As in your other question, I suggest looking at the other Paxos questions, perhaps read Paxos Made Simple.

Related

Is sharing the same database between two programming languages possible? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 11 days ago.
Improve this question
Program A is good at collecting data while Program B, in another language, is good at creating REST APIs. Is it possible to connect these two with a single database that A and B will read and write to? Performance for database operations is not really an issue in my case.
Sure this is possible. Databases typically can handle multiple connections from different programs/clients. A database does not really care which language the tool that is making the connection is written in.
Short edit:
Also most databases support "transactions". Which are used to cover that different connected clients do not break consistency of your application data while reading and writing in parallel.

In concurrent thread,how can we avoid duplicate uri in cts:uris()? [closed]

Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
In a schedular ,which is running on all host at a time, right now I am using xdmp:lock-acquire to lock the collection, so that ,cts:uris will not pick the duplicate uris, but due to this scheduler is running in sequence .Is there any other alternative ,so that I avoid this lock, so that all run in parallel.
It's a bit unclear what you are trying to do, but it sounds like you have documents in the database that you are processing using a scheduled task, that runs on all hosts. Your existing query makes it possible for two tasks to attempt to process the same document.
The easiest would be to generate a list of forests on the host that the task is running on using xdmp:host-forests, and passing that list into cts:uris as $forest-ids
$forest-ids A sequence of IDs of forests to which the search will be
constrained. An empty sequence means to search all forests in the
database. The default is ().

sql database convention [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Apologies in advance if this is a stupid question. I've more or less just started learning how to use SQL.
I'm making a website, the website stores main accounts, each having many sub-accounts associated with them. Each sub-account has a few thousand records in various tables associated with it.
My question is to do with the conventional usage of databases. Is it better to use a database per main account with everything associated with it stored in the same place, store everything in one database, or an amalgamation of both?
Some insight would be much appreciated.
Will you need to access more than one of these databases at the same time? If so put them all in one. You will not like the amount of effort and cost 'joining' them back together to do a query. On top of that, every database you have needs to be managed, and should you need to transfer data between them that can get painful as well.
Segregating data by database is a last resort.

How to write SRS for a particular task/enhancement in an application [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I need to prepare a Software Requirements Specification Document for a small enhancement within an JAVA application.
I have tried goggling for the same but found the samples for whole application whereas I am preparing SRS for a small enhancement within an application.
Can anybody suggest the links or suggestions for preparing the SRS.
As you realized by yourself what you're asked isn't a Requirements Specification, which usually covers the whole set of requirements for a software.
What you've been asked is a Change Request, and it must be merged in the existing SRS. However something tells me that there's no SRS for the software you're dealing with, as your management doesn't know the difference between both...

Client\Supplier Contact Details [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I was wondering what would be the best way to store contact details of supplier and clients.
What I was thinking was that there would be
GUID, ParentGUID,Type,TypeDesc,Details
The type would be a integer,typedesc would be for cases such as others and the details would obviously be the data.
the problem that I am finding is how to have this all linked.
This being that A client -> Contact(Title, Name,Middle,Surname) -> Phone -> Alias
This could be a hierarchy case.
As of now Supplier and Client tables cannot be joined due to backward compatibility. But will be done in the future.
Also due to certain client limitations MSSQL 2005 must be assumed as otherwise there wouldn't be a problem as this was solved in 2008 with getroot() and other useful functions.
I would have probably many cases where I would search on one of the fields. And require to know the client or supplier.
I eventually used recursive CTE for retrieving the data