You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by ashish tapdiya <as...@gmail.com> on 2015/04/03 23:45:50 UTC
understanding phoenix code flow
To understand phoenix code flow should HBase be steup in standalone or
pseudo-distributed mode
Thanks,
~Ashish
Re: understanding phoenix code flow
Posted by James Taylor <ja...@apache.org>.
+1 to Thomas' idea. Please file a new JIRA - perhaps a subtask of
PHOENIX-400 for your idea.
Thanks,
James
On Tue, Apr 7, 2015 at 11:28 AM, Thomas D'Silva <td...@salesforce.com> wrote:
> Ashish,
>
> If you want to step through server side code you can enable remote
> debugging in hbase-env.sh. I have used this with standalone mode.
>
> # Enable remote JDWP debugging of major HBase processes. Meant for
> Core Developers
> # export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS -Xdebug
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8070"
> # export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS -Xdebug
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8071"
> # export HBASE_THRIFT_OPTS="$HBASE_THRIFT_OPTS -Xdebug
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8072"
> # export HBASE_ZOOKEEPER_OPTS="$HBASE_ZOOKEEPER_OPTS -Xdebug
> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8073"
>
> There are a few existing JIRAs related to transactions PHOENIX-400,
> PHOENIX-1674, maybe you could describe your ideas there?
>
> Thanks,
> Thomas
>
>
> On Fri, Apr 3, 2015 at 3:08 PM, ashish tapdiya <as...@gmail.com> wrote:
>> Hi Jesse,
>>
>> I plan on implementing multi-row transaction support and currently trying to
>> understand code flow.
>>
>> I currently have a 6 node cluster setup. I initially linked source in the
>> client and stepped through using some simple sql workload, however, realized
>> most of the processing is done on server side.
>>
>> To be able to step through server side code, I intend to setup hbase in
>> standalone or pseudo-distributed mode.
>>
>> Thanks,
>> ~Ashish
>>
>> On Fri, Apr 3, 2015 at 4:49 PM, Jesse Yates <je...@gmail.com> wrote:
>>>
>>> You could understand it just by reading the code, or running the tests, or
>>> running a HBase minicluster in the JVM or in standalone mode or in
>>> pseudo-distributed mode or in a fully distributed setup.
>>>
>>> What are you trying to achieve?
>>>
>>> In the area you are interested in, have you:
>>> - read the docs
>>> - read the code
>>> - read though unit tests
>>> - debugged the unit tests and stepped through areas of uncertainty
>>> - written a unit test to figure out if your conjectures are correct
>>>
>>> If you are still unclear, then we can gladly help.
>>>
>>> On Fri, Apr 3, 2015 at 2:46 PM ashish tapdiya <as...@gmail.com>
>>> wrote:
>>>>
>>>> To understand phoenix code flow should HBase be steup in standalone or
>>>> pseudo-distributed mode
>>>>
>>>> Thanks,
>>>> ~Ashish
>>
>>
Re: understanding phoenix code flow
Posted by Thomas D'Silva <td...@salesforce.com>.
Ashish,
If you want to step through server side code you can enable remote
debugging in hbase-env.sh. I have used this with standalone mode.
# Enable remote JDWP debugging of major HBase processes. Meant for
Core Developers
# export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8070"
# export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8071"
# export HBASE_THRIFT_OPTS="$HBASE_THRIFT_OPTS -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8072"
# export HBASE_ZOOKEEPER_OPTS="$HBASE_ZOOKEEPER_OPTS -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8073"
There are a few existing JIRAs related to transactions PHOENIX-400,
PHOENIX-1674, maybe you could describe your ideas there?
Thanks,
Thomas
On Fri, Apr 3, 2015 at 3:08 PM, ashish tapdiya <as...@gmail.com> wrote:
> Hi Jesse,
>
> I plan on implementing multi-row transaction support and currently trying to
> understand code flow.
>
> I currently have a 6 node cluster setup. I initially linked source in the
> client and stepped through using some simple sql workload, however, realized
> most of the processing is done on server side.
>
> To be able to step through server side code, I intend to setup hbase in
> standalone or pseudo-distributed mode.
>
> Thanks,
> ~Ashish
>
> On Fri, Apr 3, 2015 at 4:49 PM, Jesse Yates <je...@gmail.com> wrote:
>>
>> You could understand it just by reading the code, or running the tests, or
>> running a HBase minicluster in the JVM or in standalone mode or in
>> pseudo-distributed mode or in a fully distributed setup.
>>
>> What are you trying to achieve?
>>
>> In the area you are interested in, have you:
>> - read the docs
>> - read the code
>> - read though unit tests
>> - debugged the unit tests and stepped through areas of uncertainty
>> - written a unit test to figure out if your conjectures are correct
>>
>> If you are still unclear, then we can gladly help.
>>
>> On Fri, Apr 3, 2015 at 2:46 PM ashish tapdiya <as...@gmail.com>
>> wrote:
>>>
>>> To understand phoenix code flow should HBase be steup in standalone or
>>> pseudo-distributed mode
>>>
>>> Thanks,
>>> ~Ashish
>
>
Re: understanding phoenix code flow
Posted by ashish tapdiya <as...@gmail.com>.
Hi Jesse,
I plan on implementing multi-row transaction support and currently trying
to understand code flow.
I currently have a 6 node cluster setup. I initially linked source in the
client and stepped through using some simple sql workload, however,
realized most of the processing is done on server side.
To be able to step through server side code, I intend to setup hbase in
standalone or pseudo-distributed mode.
Thanks,
~Ashish
On Fri, Apr 3, 2015 at 4:49 PM, Jesse Yates <je...@gmail.com> wrote:
> You could understand it just by reading the code, or running the tests, or
> running a HBase minicluster in the JVM or in standalone mode or in
> pseudo-distributed mode or in a fully distributed setup.
>
> What are you trying to achieve?
>
> In the area you are interested in, have you:
> - read the docs
> - read the code
> - read though unit tests
> - debugged the unit tests and stepped through areas of uncertainty
> - written a unit test to figure out if your conjectures are correct
>
> If you are still unclear, then we can gladly help.
>
> On Fri, Apr 3, 2015 at 2:46 PM ashish tapdiya <as...@gmail.com>
> wrote:
>
>> To understand phoenix code flow should HBase be steup in standalone or
>> pseudo-distributed mode
>>
>> Thanks,
>> ~Ashish
>>
>
Re: understanding phoenix code flow
Posted by Jesse Yates <je...@gmail.com>.
You could understand it just by reading the code, or running the tests, or
running a HBase minicluster in the JVM or in standalone mode or in
pseudo-distributed mode or in a fully distributed setup.
What are you trying to achieve?
In the area you are interested in, have you:
- read the docs
- read the code
- read though unit tests
- debugged the unit tests and stepped through areas of uncertainty
- written a unit test to figure out if your conjectures are correct
If you are still unclear, then we can gladly help.
On Fri, Apr 3, 2015 at 2:46 PM ashish tapdiya <as...@gmail.com>
wrote:
> To understand phoenix code flow should HBase be steup in standalone or
> pseudo-distributed mode
>
> Thanks,
> ~Ashish
>