Re: [VOTE] Graduate into the Phoenix project
+1 Sent from my iPhone > On 30 Oct 2019, at 21:15, Alan Gates wrote: > > I propose that the Omid project leave the incubator and become part of the > Phoenix project. The Phoenix project has proposed to incorporate both Omid > and Tephra as sub-projects. Phoenix will take over administration of the > Omid repo. Any Omid committers that request committership in Phoenix will > be granted it.[1] > > Here's my +1 on the proposal. This vote will remain open for 72 hours. > > Alan. > 1. > https://lists.apache.org/thread.html/29111aa8b59fe38ca11d6ca2f029009c437ed6986d6dcf2fb6fc5b2f@%3Cdev.phoenix.apache.org%3E
Re: Podling Omid Report Reminder - October 2019
Hi Justin, There was no progress in Omid since last month. We can submit the same report as last month, however, I assume it will be rejected again? I assume that after Phoenix releases 4.15 and 5.1, we will have more activity. Could you please advise? Thanks, Ohad On Wed, Oct 2, 2019 at 2:55 AM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 16 October 2019, 10:30 am PDT. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, October 02). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://cwiki.apache.org/confluence/display/INCUBATOR/October2019 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Note: The format of the report has changed to use markdown. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC >
[jira] [Commented] (OMID-154) Apache Incubator report - September 2019
[ https://issues.apache.org/jira/browse/OMID-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922204#comment-16922204 ] Ohad Shacham commented on OMID-154: --- Thanks [~alangates], I modified according to your request. I hope that when the next release of Phoenix will be out, people will start using Phoenix with Omid and we will have more activity in tuning, fixing bugs and implement additional features. I uploaded to the wiki page, could you please sign? - Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important unfinished issues to address before graduating: 1. Do podling name search. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? N/A How would you assess the podling's maturity? Nearing graduation Date of last release: 2019-05-21 When were the last committers or PPMC members elected? 2018-9-25 Have your mentors been helpful? Our mentors were amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. Comments: Going forward, we need to document the additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. Signed-off-by: (omid) Alan Gates Comments: (omid) James Taylor Comments: (omid) Lars Hofhansl Comments: > Apache Incubator report - September 2019 > > > Key: OMID-154 > URL: https://issues.apache.org/jira/browse/OMID-154 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for June 1, 2019 - August 31, 2019 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (OMID-154) Apache Incubator report - September 2019
[ https://issues.apache.org/jira/browse/OMID-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-154: - Assignee: Ohad Shacham > Apache Incubator report - September 2019 > > > Key: OMID-154 > URL: https://issues.apache.org/jira/browse/OMID-154 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for June 1, 2019 - August 31, 2019 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Issue Comment Deleted] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private
[
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ohad Shacham updated OMID-153:
--
Comment: was deleted
(was: Hi [~giacomotaylor], [~alangates] and [~lhofhansl],
We didn't have any progress since the last report. Could you please review the
report and comment? After your comments I will upload to the incubator webpage.
Thanks,
Ohad
)
> The method AbstractTransactionManager.closeResources should be protected
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Apache Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Priority: Minor
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in
> another package, and I was not able to because the method {{closeResources}}
> is package private instead of protected.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Issue Comment Deleted] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private
[
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ohad Shacham updated OMID-153:
--
Comment: was deleted
(was: Omid is a flexible, reliable, high performant and scalable ACID
transactional framework that allows client applications to execute transactions
on top of MVCC key/value-based NoSQL datastores (currently Apache HBase)
providing Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important unfinished issues to address before graduating:
1. Document additional features added for the integration with Apache Phoenix,
as well as, the low latency algorithm.
2. Get positive feedback from other projects currently in Apache.
3. Do podling name search.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
N/A
How has the community developed since the last report?
N/A
How would you assess the podling's maturity?
Nearing graduation
Date of last release:
2019-05-21
When were the last committers or PPMC members elected?
2018-9-25
Have your mentors been helpful?
Our mentors were amazingly helpful, they help us finding performance and
correctness bugs, as well as helped in the release process by evaluating the
release and vote internally and externally.
Signed-off-by:
(omid) Alan Gates Comments:
(omid) James Taylor Comments:
(omid) Lars Hofhansl Comments:)
> The method AbstractTransactionManager.closeResources should be protected
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Apache Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Priority: Minor
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in
> another package, and I was not able to because the method {{closeResources}}
> is package private instead of protected.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (OMID-154) Apache Incubator report - September 2019
[ https://issues.apache.org/jira/browse/OMID-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920318#comment-16920318 ] Ohad Shacham commented on OMID-154: --- Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important unfinished issues to address before graduating: 1. Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. 2. Get positive feedback from other projects currently in Apache. 3. Do podling name search. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? N/A How would you assess the podling's maturity? Nearing graduation Date of last release: 2019-05-21 When were the last committers or PPMC members elected? 2018-9-25 Have your mentors been helpful? Our mentors were amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. Signed-off-by: (omid) Alan Gates Comments: (omid) James Taylor Comments: (omid) Lars Hofhansl Comments: > Apache Incubator report - September 2019 > > > Key: OMID-154 > URL: https://issues.apache.org/jira/browse/OMID-154 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for June 1, 2019 - August 31, 2019 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OMID-154) Apache Incubator report - September 2019
[ https://issues.apache.org/jira/browse/OMID-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920319#comment-16920319 ] Ohad Shacham commented on OMID-154: --- Hi [~giacomotaylor], [~alangates] and [~lhofhansl], We didn't have any progress since the last report. Could you please review the report and comment? After your comments I will upload to the incubator webpage. Thanks, Ohad > Apache Incubator report - September 2019 > > > Key: OMID-154 > URL: https://issues.apache.org/jira/browse/OMID-154 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for June 1, 2019 - August 31, 2019 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private
[
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920317#comment-16920317
]
Ohad Shacham commented on OMID-153:
---
Hi [~giacomotaylor], [~alangates] and [~lhofhansl],
We didn't have any progress since the last report. Could you please review the
report and comment? After your comments I will upload to the incubator webpage.
Thanks,
Ohad
> The method AbstractTransactionManager.closeResources should be protected
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Apache Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Priority: Minor
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in
> another package, and I was not able to because the method {{closeResources}}
> is package private instead of protected.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (OMID-153) The method AbstractTransactionManager.closeResources should be protected instead of package private
[
https://issues.apache.org/jira/browse/OMID-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920313#comment-16920313
]
Ohad Shacham commented on OMID-153:
---
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important unfinished issues to address before graduating:
1. Document additional features added for the integration with Apache Phoenix,
as well as, the low latency algorithm.
2. Get positive feedback from other projects currently in Apache.
3. Do podling name search.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
N/A
How has the community developed since the last report?
N/A
How would you assess the podling's maturity?
Nearing graduation
Date of last release:
2019-05-21
When were the last committers or PPMC members elected?
2018-9-25
Have your mentors been helpful?
Our mentors were amazingly helpful, they help us finding performance and
correctness bugs, as well as helped in the release process by evaluating the
release and vote internally and externally.
Signed-off-by:
(omid) Alan Gates Comments:
(omid) James Taylor Comments:
(omid) Lars Hofhansl Comments:
> The method AbstractTransactionManager.closeResources should be protected
> instead of package private
> ---
>
> Key: OMID-153
> URL: https://issues.apache.org/jira/browse/OMID-153
> Project: Apache Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Robert Yokota
>Priority: Minor
>
> I was trying to subclass {{AbstractTransactionManager}} from a class in
> another package, and I was not able to because the method {{closeResources}}
> is package private instead of protected.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (OMID-154) Apache Incubator report - September 2019
Ohad Shacham created OMID-154: - Summary: Apache Incubator report - September 2019 Key: OMID-154 URL: https://issues.apache.org/jira/browse/OMID-154 Project: Apache Omid Issue Type: Task Reporter: Ohad Shacham Provide a report for June 1, 2019 - August 31, 2019 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856487#comment-16856487 ] Ohad Shacham commented on OMID-152: --- Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important unfinished issues to address before graduating: 1. Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. 2. Get positive feedback from other projects currently in Apache. 3. Do podling name search. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? 1. Lars Hofhansl returned as a mentor. 2. A new release 1.0.1 was done that contains optimisations and bug fixes for the integration with Apache Phoenix. How has the project developed since the last report? Release 1.0.1 was published and includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. How would you assess the podling's maturity? Nearing graduation Date of last release: 2019-05-21 When were the last committers or PPMC members elected? 2018-9-25 Have your mentors been helpful? Our mentors were amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. Signed-off-by: (omid) Alan Gates Comments: (omid) James Taylor Comments: (omid) Lars Hofhansl Comments: > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856476#comment-16856476 ] Ohad Shacham edited comment on OMID-152 at 6/5/19 8:15 AM: --- Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. h3. [*Three most important unfinished issues to address before graduating:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-13] # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. # Do podling name search. h3. [*Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-13] N/A h3. [*How has the community developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-13] # Lars Hofhansl returned as a mentor. # A new release 1.0.1 was done that contains optimizations and bug fixes for the integration with Apache Phoenix. h3. [*How has the project developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-13] # Release 1.0.1 was published and includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. h3. [*How would you assess the podling's maturity?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-would-you-assess-the-podlings-maturity-13] * Nearing graduation h3. [*Date of last release:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#date-of-last-release-13] 2019-05-21 h3. [*When were the last committers or PPMC members elected?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#when-were-the-last-committers-or-ppmc-members-elected-13] 2018-9-25 [*Have your mentors been helpful?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#have-your-mentors-been-helpful-13] Our mentors was amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. h3. [*Signed-off-by:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#signed-off-by-13] * (omid) Alan Gates Comments: * (omid) James Taylor Comments: * (omid) Lars Hofhansl Comments: was (Author: ohads): Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. h3. [*Three most important unfinished issues to address before graduating:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-13] # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. # Do podling name search. h3. [*Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-13] N/A h3. [*How has the community developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-13] # Lars Hofhansl returned as a mentor. # A new release 1.0.1 was done that contains optimizations and bug fixes for the integration with Apache Phoenix. h3. [*How has the project developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-13] # Release 1.0.1 was published and includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. h3. [*How would you a
[jira] [Issue Comment Deleted] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-152: -- Comment: was deleted (was: fix typos) > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856476#comment-16856476 ] Ohad Shacham edited comment on OMID-152 at 6/5/19 8:16 AM: --- fix typos was (Author: ohads): Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. h3. [*Three most important unfinished issues to address before graduating:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-13] # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. # Do podling name search. h3. [*Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-13] N/A h3. [*How has the community developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-13] # Lars Hofhansl returned as a mentor. # A new release 1.0.1 was done that contains optimizations and bug fixes for the integration with Apache Phoenix. h3. [*How has the project developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-13] # Release 1.0.1 was published and includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. h3. [*How would you assess the podling's maturity?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-would-you-assess-the-podlings-maturity-13] * Nearing graduation h3. [*Date of last release:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#date-of-last-release-13] 2019-05-21 h3. [*When were the last committers or PPMC members elected?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#when-were-the-last-committers-or-ppmc-members-elected-13] 2018-9-25 [*Have your mentors been helpful?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#have-your-mentors-been-helpful-13] Our mentors was amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. h3. [*Signed-off-by:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#signed-off-by-13] * (omid) Alan Gates Comments: * (omid) James Taylor Comments: * (omid) Lars Hofhansl Comments: > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856479#comment-16856479 ] Ohad Shacham commented on OMID-152: --- Hi [~lhofhansl], [~giacomotaylor] and [~alangates], Could you please review the report above and comments/sign? Thanks, Ohad > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-152: - Assignee: Ohad Shacham > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856476#comment-16856476 ] Ohad Shacham commented on OMID-152: --- Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. h3. [*Three most important unfinished issues to address before graduating:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#three-most-important-unfinished-issues-to-address-before-graduating-13] # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. # Do podling name search. h3. [*Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#any-issues-that-the-incubator-pmc-ipmc-or-asf-board-wishneed-to-be-aware-of-13] N/A h3. [*How has the community developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-community-developed-since-the-last-report-13] # Lars Hofhansl returned as a mentor. # A new release 1.0.1 was done that contains optimizations and bug fixes for the integration with Apache Phoenix. h3. [*How has the project developed since the last report?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-has-the-project-developed-since-the-last-report-13] # Release 1.0.1 was published and includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. h3. [*How would you assess the podling's maturity?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#how-would-you-assess-the-podlings-maturity-13] * Nearing graduation h3. [*Date of last release:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#date-of-last-release-13] 2019-05-21 h3. [*When were the last committers or PPMC members elected?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#when-were-the-last-committers-or-ppmc-members-elected-13] 2018-9-25 [*Have your mentors been helpful?*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#have-your-mentors-been-helpful-13] Our mentors was amazingly helpful, they help us finding performance and correctness bugs, as well as helped in the release process by evaluating the release and vote internally and externally. h3. [*Signed-off-by:*|https://cwiki.apache.org/confluence/display/INCUBATOR/June2019#signed-off-by-13] * (omid) Alan Gates Comments: * (omid) James Taylor Comments: * (omid) Lars Hofhansl Comments: > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OMID-152) Apache Incubator report - June 2019
Ohad Shacham created OMID-152: - Summary: Apache Incubator report - June 2019 Key: OMID-152 URL: https://issues.apache.org/jira/browse/OMID-152 Project: Apache Omid Issue Type: Task Reporter: Ohad Shacham -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-152) Apache Incubator report - June 2019
[ https://issues.apache.org/jira/browse/OMID-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-152: -- Description: Provide a report for March 1, 2019 - May 31, 2019 > Apache Incubator report - June 2019 > --- > > Key: OMID-152 > URL: https://issues.apache.org/jira/browse/OMID-152 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for March 1, 2019 - May 31, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-56) Integrate with Apache Phoenix
[ https://issues.apache.org/jira/browse/OMID-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham closed OMID-56. > Integrate with Apache Phoenix > - > > Key: OMID-56 > URL: https://issues.apache.org/jira/browse/OMID-56 > Project: Apache Omid > Issue Type: Improvement >Reporter: James Taylor > Assignee: Ohad Shacham >Priority: Major > Labels: phoenix > > The current transaction implementation in Phoenix uses Tephra which is good > when the number of rows in the transaction is small and the changes of a > conflict are relatively rare. It's also not clear when the number of > simultaneous transactions would max out given the single, global transaction > manager component. > Omid is very complimentary in this regard. Though the overhead for small > transactions may be larger than Tephra, it will likely scale well as the > number of rows in a transaction grows and has no global transaction manager. > It'd be great to figure out the best way to integrate Omid with Phoenix. The > trickiest issue may be with optimizing secondary indexes, in that conflict > detection is not necessary for them. We could leave this optimization for the > future and just treat them as any other HBase table. Perhaps a good first > step would be to just turn on Omid transactions at the HBase level and then > have Phoenix issue the appropriate Omid call for start transaction, commit > transaction, and rollback transaction. It might just work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-56) Integrate with Apache Phoenix
[ https://issues.apache.org/jira/browse/OMID-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-56: Assignee: Ohad Shacham > Integrate with Apache Phoenix > - > > Key: OMID-56 > URL: https://issues.apache.org/jira/browse/OMID-56 > Project: Apache Omid > Issue Type: Improvement >Reporter: James Taylor > Assignee: Ohad Shacham >Priority: Major > Labels: phoenix > > The current transaction implementation in Phoenix uses Tephra which is good > when the number of rows in the transaction is small and the changes of a > conflict are relatively rare. It's also not clear when the number of > simultaneous transactions would max out given the single, global transaction > manager component. > Omid is very complimentary in this regard. Though the overhead for small > transactions may be larger than Tephra, it will likely scale well as the > number of rows in a transaction grows and has no global transaction manager. > It'd be great to figure out the best way to integrate Omid with Phoenix. The > trickiest issue may be with optimizing secondary indexes, in that conflict > detection is not necessary for them. We could leave this optimization for the > future and just treat them as any other HBase table. Perhaps a good first > step would be to just turn on Omid transactions at the HBase level and then > have Phoenix issue the appropriate Omid call for start transaction, commit > transaction, and rollback transaction. It might just work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-56) Integrate with Apache Phoenix
[ https://issues.apache.org/jira/browse/OMID-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-56. -- Resolution: Fixed > Integrate with Apache Phoenix > - > > Key: OMID-56 > URL: https://issues.apache.org/jira/browse/OMID-56 > Project: Apache Omid > Issue Type: Improvement >Reporter: James Taylor > Assignee: Ohad Shacham >Priority: Major > Labels: phoenix > > The current transaction implementation in Phoenix uses Tephra which is good > when the number of rows in the transaction is small and the changes of a > conflict are relatively rare. It's also not clear when the number of > simultaneous transactions would max out given the single, global transaction > manager component. > Omid is very complimentary in this regard. Though the overhead for small > transactions may be larger than Tephra, it will likely scale well as the > number of rows in a transaction grows and has no global transaction manager. > It'd be great to figure out the best way to integrate Omid with Phoenix. The > trickiest issue may be with optimizing secondary indexes, in that conflict > detection is not necessary for them. We could leave this optimization for the > future and just treat them as any other HBase table. Perhaps a good first > step would be to just turn on Omid transactions at the HBase level and then > have Phoenix issue the appropriate Omid call for start transaction, commit > transaction, and rollback transaction. It might just work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-150) Validate transaction on the fly
[ https://issues.apache.org/jira/browse/OMID-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849194#comment-16849194 ] Ohad Shacham commented on OMID-150: --- [~lhofhansl], do you mean doing the commit without accessing the tso? This can currently be done only for single entry read/write. Or do you refer to keeping only the row level information in the client conflict set and read the written entries when setting the shadow cells at the asynchronous post commit? > Validate transaction on the fly > --- > > Key: OMID-150 > URL: https://issues.apache.org/jira/browse/OMID-150 > Project: Apache Omid > Issue Type: Wish >Reporter: Lars Hofhansl >Priority: Major > > Another brainstorming idea: Can we validate transactions on the go? That way > we do not have the client/tso as a scale limit to how big transactions can be. > I briefly discussed this [~ohads]. Although I didn't quite get the details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-147) Discuss better/faster ways of garbage collection during HBase major compactions
[ https://issues.apache.org/jira/browse/OMID-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849190#comment-16849190 ] Ohad Shacham commented on OMID-147: --- [~lhofhansl], so we have two problem in here, data that was deleted and should be gc and transaction that can write "forever" and write the data, in a previous timestamp, after it was deleted, even though if this transaction will never be able to commit? Am I write? As you said, the first problem should be done by configuration the low watermark to be max (time interval, timestamp of data evicted from the conflict map). The second, should be done by adding a suicide mechanism to transactions? > Discuss better/faster ways of garbage collection during HBase major > compactions > --- > > Key: OMID-147 > URL: https://issues.apache.org/jira/browse/OMID-147 > Project: Apache Omid > Issue Type: Wish >Affects Versions: 1.0.1 >Reporter: Lars Hofhansl >Priority: Major > > *Not for 1.0.1* > In our use of HBase/Phoenix we very frequently need to delete a lot of data > (customers leave, we have GDPR requests and various other reasons). > We need to be able to ensure that data marked for deletion in HBase is > removed no later than some specific point in time. Currently this is hard to > achieve - see OMID-142. > So let's have a discussion here, about how this could happen. Either by some > manual step, or -preferably - by disconnecting the conflictMap from when a > transaction's deleted data becomes eligible for physical removal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [VOTE] Omid release branch 1.0.1
+1 verified, compiled and ran tests. On Wed, May 1, 2019 at 8:20 PM la...@apache.org wrote: > +1 > I've been running this version with Phoenix for a while.I tried small and > large transactions, tested the conflict checking, snapshotting > (checkpointing), all works fine, nothing undue in the logs. > > Thanks for working with me to address/commit all the various I found in > Omid 1.0.0. > -- Lars > On Wednesday, May 1, 2019, 6:53:49 AM EDT, Yoni Gottesman < > yon...@apache.org> wrote: > > updated hash to sh512: > > https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz.sha512 > > On Wed, May 1, 2019 at 10:46 AM Yoni Gottesman wrote: > > > Here's the Apache Omid 1.0.1 release candidate #0 now available for a > vote > > within dev community. > > > > Links to various release artifacts are given below. Please review and > vote. > > > > The vote will be open for at least 72 hours and until necessary number of > > votes are reached. > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Here is my +1 > > > > Release notes for the 1.0.1 release: > https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/RELEASE_NOTES.html > > > > Git tag for the release: > https://git-wip-us.apache.org/repos/asf?p=incubator-omid.git;a=tag;h=aca4d171b12cc18b8cd482e5f2411b86be1b17e5 > > Sources for the release: > https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz > > > > Source release verification: > > PGP Signature: > https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz.asc > > > > MD5 Hash: > https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/apache-omid-incubating-1.0.1-src.tar.gz.md5 > > > > Keys to verify the signature of the release artifact are available at: > https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.1-rc0/KEYS > > > > >
[jira] [Commented] (OMID-146) Persist transaction commit before updating low watermark
[ https://issues.apache.org/jira/browse/OMID-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824910#comment-16824910 ] Ohad Shacham commented on OMID-146: --- [~yonigo], I did a review, please fix and commit. Thx! > Persist transaction commit before updating low watermark > > > Key: OMID-146 > URL: https://issues.apache.org/jira/browse/OMID-146 > Project: Apache Omid > Issue Type: Bug > Reporter: Ohad Shacham >Assignee: Yonatan Gottesman >Priority: Minor > Fix For: 1.0.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > When a transaction t updates the conflict table at the TSO, it mights remove > entries of transactions that committed after t started, or even entries of t. > Therefore, in order to make sure that the garbage collector does not removes > entries of t from the data tables, thinking accidentally that t was not > committed yet. We should first persist t's commit in the commit table and > only then update the low watermark. This also applies to the low latency > which persists the commit by the clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-146) Persist transaction commit before updating low watermark
[
https://issues.apache.org/jira/browse/OMID-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824907#comment-16824907
]
Ohad Shacham commented on OMID-146:
---
{quote}Also, will the commit cache be a problem now? As we run the
CompactScanner, once we cache a commit ts as absent, we won't check it again,
right?
{quote}
It is not a problem, since we cache a commit as absent only after invalidation.
Which means that this transaction won't be able to commit anymore. This is
basically needed only for the low latency mode. For the regular mode, we
guarantee that the low water mark is persisted only after all the previous
commit persisted and also transaction that started before the low water mark is
aborted on commit request.
> Persist transaction commit before updating low watermark
>
>
> Key: OMID-146
> URL: https://issues.apache.org/jira/browse/OMID-146
> Project: Apache Omid
> Issue Type: Bug
>Reporter: Ohad Shacham
>Assignee: Yonatan Gottesman
>Priority: Minor
> Fix For: 1.0.1
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> When a transaction t updates the conflict table at the TSO, it mights remove
> entries of transactions that committed after t started, or even entries of t.
> Therefore, in order to make sure that the garbage collector does not removes
> entries of t from the data tables, thinking accidentally that t was not
> committed yet. We should first persist t's commit in the commit table and
> only then update the low watermark. This also applies to the low latency
> which persists the commit by the clients.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820383#comment-16820383 ] Ohad Shacham commented on OMID-145: --- No, the invalidation occurs only on transactions that started before the low water mark. > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: compactionTiming.png, omid-145.patch > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819796#comment-16819796 ] Ohad Shacham commented on OMID-145: --- Good question, the compaction checks only whether transactions that started below the low water mark are committed. The data of the ones that started after the low water mark are kept and we don't care whether these are committed or not. Basically, transactions that started below the low water mark are aborted so they should not influence the cache. There was a little race that we thought about and opened OMID-146 because of it. After this fix, transaction won't be able to commit if the low water mark is after its begin timestamp. > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: compactionTiming.png, omid-145.patch > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-146) Persist transaction commit before updating low watermark
[ https://issues.apache.org/jira/browse/OMID-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-146: - Assignee: Yonatan Gottesman > Persist transaction commit before updating low watermark > > > Key: OMID-146 > URL: https://issues.apache.org/jira/browse/OMID-146 > Project: Apache Omid > Issue Type: Bug > Reporter: Ohad Shacham >Assignee: Yonatan Gottesman >Priority: Minor > > When a transaction t updates the conflict table at the TSO, it mights remove > entries of transactions that committed after t started, or even entries of t. > Therefore, in order to make sure that the garbage collector does not removes > entries of t from the data tables, thinking accidentally that t was not > committed yet. We should first persist t's commit in the commit table and > only then update the low watermark. This also applies to the low latency > which persists the commit by the clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-146) Persist transaction commit before updating low watermark
[ https://issues.apache.org/jira/browse/OMID-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-146: -- Fix Version/s: 1.0.1 > Persist transaction commit before updating low watermark > > > Key: OMID-146 > URL: https://issues.apache.org/jira/browse/OMID-146 > Project: Apache Omid > Issue Type: Bug > Reporter: Ohad Shacham >Assignee: Yonatan Gottesman >Priority: Minor > Fix For: 1.0.1 > > > When a transaction t updates the conflict table at the TSO, it mights remove > entries of transactions that committed after t started, or even entries of t. > Therefore, in order to make sure that the garbage collector does not removes > entries of t from the data tables, thinking accidentally that t was not > committed yet. We should first persist t's commit in the commit table and > only then update the low watermark. This also applies to the low latency > which persists the commit by the clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OMID-146) Persist transaction commit before updating low watermark
Ohad Shacham created OMID-146: - Summary: Persist transaction commit before updating low watermark Key: OMID-146 URL: https://issues.apache.org/jira/browse/OMID-146 Project: Apache Omid Issue Type: Bug Reporter: Ohad Shacham When a transaction t updates the conflict table at the TSO, it mights remove entries of transactions that committed after t started, or even entries of t. Therefore, in order to make sure that the garbage collector does not removes entries of t from the data tables, thinking accidentally that t was not committed yet. We should first persist t's commit in the commit table and only then update the low watermark. This also applies to the low latency which persists the commit by the clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818894#comment-16818894 ] Ohad Shacham commented on OMID-145: --- [~yonigo], the patch looks good. > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: compactionTiming.png, omid-145.patch > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818893#comment-16818893 ] Ohad Shacham commented on OMID-145: --- A transaction is aborted if its start timestamp is smaller than the low water mark. The reason is that entries that were committed after the transaction started were removed from the conflict table and we can accidentally think that the transaction can safely commit even though it had a conflict with one of the entries that were removed. So all transactions that started before the low water mark are aborted. > And so I should roughly size the conflict map to the maximum expected number >of rows in flight? Something like this :), the conflict table is a bounded hash of bins so you don't have any guarantees... but something like this can be good. > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: compactionTiming.png, omid-145.patch > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818279#comment-16818279 ] Ohad Shacham commented on OMID-145: --- Any transaction t over 100k will force all current inflight transaction to fail, however, t will pass. The reason is that after t's conflict analysis will pass it will get a commit timestamp c, which is the latest one. Then its 200 keys will be added to the conflict table one by one with commit time stamp c. Once one of t's key's will be removed from the conflict table the low water mark will be set to c. t will still pass since the decision for its commit was already made, however, all the inflight transactions will be aborted since their start timestamps are smaller than c. Thanks for finding all these bugs, it is great! > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: compactionTiming.png > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-145: -- Fix Version/s: 1.0.1 > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: compactionTiming.png > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-145) High CPU usage during compactions.
[ https://issues.apache.org/jira/browse/OMID-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817998#comment-16817998 ] Ohad Shacham commented on OMID-145: --- What is the size of the conflict table you are using? I understood that you reduced the size in order to get a better GC. However, a better GC means increasing the low water mark more frequently that might increase the abort ratio. The async post commit can be the reason, as you said, however, you should make sure that the size of the conflict table is not too small and cause to many aborts. [~lhofhansl], is it OK with you that we ([~yonigo] :)) will add the caches in here and then we will start the 1.0.1 release vote? We would like to make an Omid release for the coming Phoenix release. Have you noticed any other urgent issues? > High CPU usage during compactions. > -- > > Key: OMID-145 > URL: https://issues.apache.org/jira/browse/OMID-145 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Major > Attachments: compactionTiming.png > > > See attached image, almost all (96%!!) of the compaction time is spent in > org.apache.hadoop.hbase.regionserver.CompactorScanner.queryCommitTimestamp() > I guess that's when the shadowCell is not yet present. > We already have problems with long compactions in HBase, prolonging these > potentially by 25x (all the rest of the compaction logic took only 4% of the > time), would not be a pleasant idea. > Perhaps we can do that same caching we do with the commit cache during > regular scanning...? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-131) Enhance row level conlict detection to reduce client memory footprint.
[ https://issues.apache.org/jira/browse/OMID-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817232#comment-16817232 ] Ohad Shacham commented on OMID-131: --- The reason is that now you have the same shadow cell for different columns. When you do a get/scan in Omid, you ask to get the shadow cells for the rows you are looking for. In the new scheme we will ask to get the row or row/family shadow cell for the cells we are looking for and these might be in version higher than the cell we are looking for. Lets take the following example: For row R with columns c1 and c2, assume we write R with c1 at version 1 and R with c2 with version 2. With the current scheme we will have: R c1 c1_shadow - version 1 R c2 c2_shadow - version 2. Reading c1 will return c1 and c1_shadow from version 1. Changing the scheme will results in: R c1 R_shadow - version 1 R c2 R_shadow - version 2. Reading c1 will return c1 from version 1 and R_shadow from version 2 and we will need to reread R_shadow again to find R_shadow from version 1. > Enhance row level conlict detection to reduce client memory footprint. > -- > > Key: OMID-131 > URL: https://issues.apache.org/jira/browse/OMID-131 > Project: Apache Omid > Issue Type: Improvement >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently even if omid is working in row level conflict detection, all the > cells are kept by the client until after commit for writing shadow cells or > removing them after abort. > Instead the client should store only the rows or only the family. > If we choose to store only the row, the client memory footprint will be > smaller, but if a region server wants to query a shadow cell for a cell it > might have to query a different region. > On the other hand client can store the famelies of a writeset. This will have > a bigger footprint if we have lots of families but if a region queries a > shadow cell it will be on the same region. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-144) Read from commit table doesnt remove checkpoint bits
[ https://issues.apache.org/jira/browse/OMID-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817207#comment-16817207 ] Ohad Shacham commented on OMID-144: --- +1 > Read from commit table doesnt remove checkpoint bits > > > Key: OMID-144 > URL: https://issues.apache.org/jira/browse/OMID-144 > Project: Apache Omid > Issue Type: Bug >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid_144.patch > > > Related to PHOENIX-5233. > When a read is done to the commit table there are cases that the checkpoint > bits are not cleared > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-143) Netty preventing HBase regionserver from exiting.
[
https://issues.apache.org/jira/browse/OMID-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ohad Shacham closed OMID-143.
-
Resolution: Cannot Reproduce
> Netty preventing HBase regionserver from exiting.
> -
>
> Key: OMID-143
> URL: https://issues.apache.org/jira/browse/OMID-143
> Project: Apache Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Lars Hofhansl
>Priority: Major
>
> Sorry for the barrage of issues... But once I'm on the roll...
> I found this:
> {code}
> "Hashed wheel timer #3" #10789 prio=5 os_prio=0 tid=0x7f24c4d01800
> nid=0x915e waiting on condition [0x7f247b166000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.jboss.netty.util.HashedWheelTimer$Worker.waitForNextTick(HashedWheelTimer.java:459)
> at
> org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:376)
> at
> org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Preventing the regionserver from exiting. HBase now uses Netty 4.1, which
> used io.netty..., so this must be due to Omid's usage of Netty.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OMID-131) Enhance row level conlict detection to reduce client memory footprint.
[ https://issues.apache.org/jira/browse/OMID-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817206#comment-16817206 ] Ohad Shacham commented on OMID-131: --- It is a tradeoff between using HBase storage and returning Tephra's lists in each begin. Switching to row level will reduce the storage, however, might increase the scan/get times. > Enhance row level conlict detection to reduce client memory footprint. > -- > > Key: OMID-131 > URL: https://issues.apache.org/jira/browse/OMID-131 > Project: Apache Omid > Issue Type: Improvement >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently even if omid is working in row level conflict detection, all the > cells are kept by the client until after commit for writing shadow cells or > removing them after abort. > Instead the client should store only the rows or only the family. > If we choose to store only the row, the client memory footprint will be > smaller, but if a region server wants to query a shadow cell for a cell it > might have to query a different region. > On the other hand client can store the famelies of a writeset. This will have > a bigger footprint if we have lots of families but if a region queries a > shadow cell it will be on the same region. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-142) Omid GC fails in Phoenix does not remove all data
[ https://issues.apache.org/jira/browse/OMID-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-142: -- Fix Version/s: 1.0.1 > Omid GC fails in Phoenix does not remove all data > - > > Key: OMID-142 > URL: https://issues.apache.org/jira/browse/OMID-142 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: 142-test.txt, omid142.patch > > > When you insert a bunch of data into a table, followed by a DELETE FROM > , then flush and compact the table in HBase, the data is not removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-139) Rollback is extremely slow
[ https://issues.apache.org/jira/browse/OMID-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-139: -- Fix Version/s: 1.0.1 > Rollback is extremely slow > -- > > Key: OMID-139 > URL: https://issues.apache.org/jira/browse/OMID-139 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Lars Hofhansl >Priority: Major > Fix For: 1.0.1 > > Attachments: 138_139.patch > > > Almost 3 minutes for about 100k rows. > Haven't debugged it, yet, but it is possible that this is not batching the > cleanup and doing individual RPCs? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-139) Rollback is extremely slow
[ https://issues.apache.org/jira/browse/OMID-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-139: - Assignee: Yonatan Gottesman > Rollback is extremely slow > -- > > Key: OMID-139 > URL: https://issues.apache.org/jira/browse/OMID-139 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: 138_139.patch > > > Almost 3 minutes for about 100k rows. > Haven't debugged it, yet, but it is possible that this is not batching the > cleanup and doing individual RPCs? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-137) collections4.map.LRUMap is missing in 1.0.1
[
https://issues.apache.org/jira/browse/OMID-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ohad Shacham updated OMID-137:
--
Fix Version/s: 1.0.1
> collections4.map.LRUMap is missing in 1.0.1
> ---
>
> Key: OMID-137
> URL: https://issues.apache.org/jira/browse/OMID-137
> Project: Apache Omid
> Issue Type: Bug
>Affects Versions: 1.0.1
>Reporter: Lars Hofhansl
>Priority: Major
> Fix For: 1.0.1
>
> Attachments: phoenix_omid_101.patch
>
>
> Just tried running with 1.0.1 and HBase 1.5.0 and Phoenix 4.15.0 and I see
> this in the region server. Looks like it forgets to pull in the LRUMap
> dependency.
> {code}
> 2019-03-29 19:17:09,491 ERROR
> [RpcServer.default.FPBQ.Fifo.handler=29,queue=2,po
> rt=16201] coprocessor.CoprocessorHost: The coprocessor
> org.apache.phoenix.coproc
> essor.OmidTransactionalProcessor threw java.lang.NoClassDefFoundError:
> org/apach
> e/commons/collections4/map/LRUMap
> java.lang.NoClassDefFoundError: org/apache/commons/collections4/map/LRUMap
> at
> org.apache.omid.transaction.TransactionVisibilityFilterBase.(Tr
> ansactionVisibilityFilterBase.java:59)
> at
> org.apache.omid.transaction.TransactionFilters.getVisibilityFilter(Tr
> ansactionFilters.java:29)
> at
> org.apache.omid.transaction.OmidSnapshotFilter.preScannerOpen(OmidSna
> pshotFilter.java:164)
> at
> org.apache.omid.transaction.OmidSnapshotFilter.preScannerOpen(OmidSnapshotFilter.java:146)
> at
> org.apache.phoenix.coprocessor.DelegateRegionObserver.preScannerOpen(DelegateRegionObserver.java:571)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OMID-126) Client leaks executor / timer thread
[ https://issues.apache.org/jira/browse/OMID-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-126. --- Resolution: Fixed > Client leaks executor / timer thread > > > Key: OMID-126 > URL: https://issues.apache.org/jira/browse/OMID-126 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Philippe Laflamme >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: OMID-126.patch > > > Each instance of ConnectionFailedState creates a timer, but nothing ever > cleans them up. > A patch is provided here: https://github.com/apache/incubator-omid/pull/53 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-125) TSO panic in lease manager causes deadlock
[ https://issues.apache.org/jira/browse/OMID-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-125. --- Resolution: Fixed > TSO panic in lease manager causes deadlock > -- > > Key: OMID-125 > URL: https://issues.apache.org/jira/browse/OMID-125 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Philippe Laflamme >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: OMID-125.patch > > > When the TSO loses its lease, it panics and invokes the panicker. The default > SystemExitPanicker calls System.exit synchronously which, in turn, calls the > shutdown hooks synchronously. > This causes the shutdown hooks to run within the Lease management scheduler's > lock which is also required to run shutdown. > To replicate the issue: > * start the tso server in HA > * from a ZK shell, update the tso-lease node: > ** get /omid/tso-lease > ** set /omid/tso-lease > * the tso server will panic but fail to shutdown properly > A patch is provided here https://github.com/apache/incubator-omid/pull/52 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-129) Omid VisibilityFilter should cache uncommitted transactions
[ https://issues.apache.org/jira/browse/OMID-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-129. --- Resolution: Fixed > Omid VisibilityFilter should cache uncommitted transactions > --- > > Key: OMID-129 > URL: https://issues.apache.org/jira/browse/OMID-129 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid129.patch > > > When the TransactionVisibilityFilterBase encounters a cell of an uncommitted > transaction, store that starts TS in the commit cache with commit timestamp > Long.MAX_VALUE. > With this cache when scanning through lots of uncommitted values omid wont > have to go to the commit table for every cell. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-124) HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads
[ https://issues.apache.org/jira/browse/OMID-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-124. --- Resolution: Fixed > HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads > -- > > Key: OMID-124 > URL: https://issues.apache.org/jira/browse/OMID-124 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Critical > Fix For: 1.0.1 > > Attachments: OMID-124.txt, omid124.patch > > > I found that as soon as any transaction is written in HBase, the region > server subsequently fails to shut down. > I tracked it down the HBaseClient in HBaseCommitTable. I think this should > generally create daemon threads only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-126) Client leaks executor / timer thread
[ https://issues.apache.org/jira/browse/OMID-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-126: - Assignee: Yonatan Gottesman > Client leaks executor / timer thread > > > Key: OMID-126 > URL: https://issues.apache.org/jira/browse/OMID-126 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Philippe Laflamme >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: OMID-126.patch > > > Each instance of ConnectionFailedState creates a timer, but nothing ever > cleans them up. > A patch is provided here: https://github.com/apache/incubator-omid/pull/53 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-125) TSO panic in lease manager causes deadlock
[ https://issues.apache.org/jira/browse/OMID-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797012#comment-16797012 ] Ohad Shacham commented on OMID-125: --- LGTM +1 > TSO panic in lease manager causes deadlock > -- > > Key: OMID-125 > URL: https://issues.apache.org/jira/browse/OMID-125 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Philippe Laflamme >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: OMID-125.patch > > > When the TSO loses its lease, it panics and invokes the panicker. The default > SystemExitPanicker calls System.exit synchronously which, in turn, calls the > shutdown hooks synchronously. > This causes the shutdown hooks to run within the Lease management scheduler's > lock which is also required to run shutdown. > To replicate the issue: > * start the tso server in HA > * from a ZK shell, update the tso-lease node: > ** get /omid/tso-lease > ** set /omid/tso-lease > * the tso server will panic but fail to shutdown properly > A patch is provided here https://github.com/apache/incubator-omid/pull/52 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-126) Client leaks executor / timer thread
[ https://issues.apache.org/jira/browse/OMID-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797011#comment-16797011 ] Ohad Shacham commented on OMID-126: --- LGTM +1 > Client leaks executor / timer thread > > > Key: OMID-126 > URL: https://issues.apache.org/jira/browse/OMID-126 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Philippe Laflamme >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: OMID-126.patch > > > Each instance of ConnectionFailedState creates a timer, but nothing ever > cleans them up. > A patch is provided here: https://github.com/apache/incubator-omid/pull/53 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-132) post commit batch sc writes
[ https://issues.apache.org/jira/browse/OMID-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-132. --- Resolution: Fixed > post commit batch sc writes > --- > > Key: OMID-132 > URL: https://issues.apache.org/jira/browse/OMID-132 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid132.patch > > Time Spent: 20m > Remaining Estimate: 0h > > The new hbase Table interface doesnt batch so we need to batch the writes in > omid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-129) Omid VisibilityFilter should cache uncommitted transactions
[ https://issues.apache.org/jira/browse/OMID-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797010#comment-16797010 ] Ohad Shacham commented on OMID-129: --- LGTM +1 > Omid VisibilityFilter should cache uncommitted transactions > --- > > Key: OMID-129 > URL: https://issues.apache.org/jira/browse/OMID-129 > Project: Apache Omid > Issue Type: Sub-task >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid129.patch > > > When the TransactionVisibilityFilterBase encounters a cell of an uncommitted > transaction, store that starts TS in the commit cache with commit timestamp > Long.MAX_VALUE. > With this cache when scanning through lots of uncommitted values omid wont > have to go to the commit table for every cell. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-135) Omid compaction deletes shadow cells
[ https://issues.apache.org/jira/browse/OMID-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-135. --- Resolution: Fixed > Omid compaction deletes shadow cells > > > Key: OMID-135 > URL: https://issues.apache.org/jira/browse/OMID-135 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid135.patch > > > Therea re two bugs in compactorScanner: > 1) when the limit is -1 and exception is raised when calling List:subList(). > 2) The CellUtils:mapCellsToShadowCells doesnt create the map correctly if the > shadow cells come before regular cells in the scan order. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-133) TTable flush before get()/scan() when autoFlush is false
[ https://issues.apache.org/jira/browse/OMID-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-133. --- Resolution: Fixed > TTable flush before get()/scan() when autoFlush is false > > > Key: OMID-133 > URL: https://issues.apache.org/jira/browse/OMID-133 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid133.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-132) post commit batch sc writes
[ https://issues.apache.org/jira/browse/OMID-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797000#comment-16797000 ] Ohad Shacham commented on OMID-132: --- LGTM +1 > post commit batch sc writes > --- > > Key: OMID-132 > URL: https://issues.apache.org/jira/browse/OMID-132 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid132.patch > > Time Spent: 20m > Remaining Estimate: 0h > > The new hbase Table interface doesnt batch so we need to batch the writes in > omid -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-131) Enhance row level conlict detection to reduce client memory footprint.
[ https://issues.apache.org/jira/browse/OMID-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-131: -- Fix Version/s: (was: 1.0.1) > Enhance row level conlict detection to reduce client memory footprint. > -- > > Key: OMID-131 > URL: https://issues.apache.org/jira/browse/OMID-131 > Project: Apache Omid > Issue Type: Improvement >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Currently even if omid is working in row level conflict detection, all the > cells are kept by the client until after commit for writing shadow cells or > removing them after abort. > Instead the client should store only the rows or only the family. > If we choose to store only the row, the client memory footprint will be > smaller, but if a region server wants to query a shadow cell for a cell it > might have to query a different region. > On the other hand client can store the famelies of a writeset. This will have > a bigger footprint if we have lots of families but if a region queries a > shadow cell it will be on the same region. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-134) TransactionManager should be thread safe
[ https://issues.apache.org/jira/browse/OMID-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-134. --- Resolution: Fixed > TransactionManager should be thread safe > > > Key: OMID-134 > URL: https://issues.apache.org/jira/browse/OMID-134 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid134.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > It seems that phoenix shares a transactionmanager for all threads. > This mean the tm should be thread safe. Some hbase Table should be created on > demand so that they are not shared between threads -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-134) TransactionManager should be thread safe
[ https://issues.apache.org/jira/browse/OMID-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796995#comment-16796995 ] Ohad Shacham commented on OMID-134: --- LGTM +1 > TransactionManager should be thread safe > > > Key: OMID-134 > URL: https://issues.apache.org/jira/browse/OMID-134 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid134.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > It seems that phoenix shares a transactionmanager for all threads. > This mean the tm should be thread safe. Some hbase Table should be created on > demand so that they are not shared between threads -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-135) Omid compaction deletes shadow cells
[ https://issues.apache.org/jira/browse/OMID-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796955#comment-16796955 ] Ohad Shacham commented on OMID-135: --- LGTM +1 > Omid compaction deletes shadow cells > > > Key: OMID-135 > URL: https://issues.apache.org/jira/browse/OMID-135 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid135.patch > > > Therea re two bugs in compactorScanner: > 1) when the limit is -1 and exception is raised when calling List:subList(). > 2) The CellUtils:mapCellsToShadowCells doesnt create the map correctly if the > shadow cells come before regular cells in the scan order. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham closed OMID-136. - > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-136. --- Resolution: Fixed > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786540#comment-16786540 ] Ohad Shacham commented on OMID-136: --- Thanks for signing the report. > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784812#comment-16784812 ] Ohad Shacham commented on OMID-136: --- https://wiki.apache.org/incubator/March2019 > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782647#comment-16782647 ] Ohad Shacham edited comment on OMID-136 at 3/5/19 7:48 AM: --- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: # Optimise Omid for the integration with Apache Phoenix. # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? # Integration with Apache Phoenix was over, we are currently working on optimisation. How has the project developed since the last report? # Release 1.0.0 was published and includes all the Phoenix required features. # The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. # We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Mature for graduation. Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [] Community building [X ] Nearing graduation [ ] Other: Date of last release: 2018-12-04 When were the last committers or PPMC members elected? 2018-9-25 Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) James Taylor Comments: was (Author: ohads): Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: # Optimized Omid for the integration with Apache Phoenix. # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? # Integration with Apache Phoenix was over, we are currently working on optimization. How has the project developed since the last report? # Release 1.0.0 was published and includes all the Phoenix required features. # The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. # We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [] Community building [X ] Nearing graduation [ ] Other: Date of last release: 2018-12-04 When were the last committers or PPMC members elected? 2018-9-25 Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) James Taylor Comments: > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task >Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782647#comment-16782647 ] Ohad Shacham edited comment on OMID-136 at 3/5/19 7:50 AM: --- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: # Optimise Omid for the integration with Apache Phoenix. # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? # Integration with Apache Phoenix was over, we are currently working on optimisation. How has the project developed since the last report? # Release 1.0.0 was published and includes all the Phoenix required features. # The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. # We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [] Community building [X ] Nearing graduation [ ] Other: Date of last release: 2018-12-04 When were the last committers or PPMC members elected? 2018-9-25 Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) James Taylor Comments: was (Author: ohads): Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: # Optimise Omid for the integration with Apache Phoenix. # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? # Integration with Apache Phoenix was over, we are currently working on optimisation. How has the project developed since the last report? # Release 1.0.0 was published and includes all the Phoenix required features. # The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. # We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Mature for graduation. Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [] Community building [X ] Nearing graduation [ ] Other: Date of last release: 2018-12-04 When were the last committers or PPMC members elected? 2018-9-25 Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) James Taylor Comments: > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task >Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782651#comment-16782651 ] Ohad Shacham commented on OMID-136: --- Hi [~giacomotaylor] and [~alangates], Could you please review the report? I will upload to the wiki after your comments. Thanks, Ohad > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782647#comment-16782647 ] Ohad Shacham commented on OMID-136: --- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: # Optimized Omid for the integration with Apache Phoenix. # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? # Integration with Apache Phoenix was over, we are currently working on optimization. How has the project developed since the last report? # Release 1.0.0 was published and includes all the Phoenix required features. # The Apache Phoenix code that uses Omid was committed and currently Omid serves as Phoenix transaction processor. # We are currently working on a minor release in Omid, 1.0.1, that includes optimization to Omid that inferred from the integration with Phoenix. These features mostly improve the performance of Omid, however, some are bug fixes that revealed by the integration with Phoenix while pushing Omid to its corner cases. We will start the release process in a few days. Jiras 124 - 135 will be part of the release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [] Community building [X ] Nearing graduation [ ] Other: Date of last release: 2018-12-04 When were the last committers or PPMC members elected? 2018-9-25 Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) James Taylor Comments: > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-136) Apache Incubator report - March 2019
[ https://issues.apache.org/jira/browse/OMID-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-136: - Assignee: Ohad Shacham > Apache Incubator report - March 2019 > > > Key: OMID-136 > URL: https://issues.apache.org/jira/browse/OMID-136 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OMID-136) Apache Incubator report - March 2019
Ohad Shacham created OMID-136: - Summary: Apache Incubator report - March 2019 Key: OMID-136 URL: https://issues.apache.org/jira/browse/OMID-136 Project: Apache Omid Issue Type: Task Reporter: Ohad Shacham Provide a report for December 1, 2018 - February 28, 2019 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-134) TransactionManager should be thread safe
[ https://issues.apache.org/jira/browse/OMID-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777851#comment-16777851 ] Ohad Shacham commented on OMID-134: --- [~yonigo], could you please create a pull request? Thx! > TransactionManager should be thread safe > > > Key: OMID-134 > URL: https://issues.apache.org/jira/browse/OMID-134 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid134.patch > > > It seems that phoenix shares a transactionmanager for all threads. > This mean the tm should be thread safe. Some hbase Table should be created on > demand so that they are not shared between threads -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-133) TTable flush before get()/scan() when autoFlush is false
[ https://issues.apache.org/jira/browse/OMID-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777848#comment-16777848 ] Ohad Shacham commented on OMID-133: --- +1, please commit. > TTable flush before get()/scan() when autoFlush is false > > > Key: OMID-133 > URL: https://issues.apache.org/jira/browse/OMID-133 > Project: Apache Omid > Issue Type: Bug >Affects Versions: 1.0.1 >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > Attachments: omid133.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-130) Phoenix integration issues
[ https://issues.apache.org/jira/browse/OMID-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-130: -- Fix Version/s: 1.0.1 > Phoenix integration issues > -- > > Key: OMID-130 > URL: https://issues.apache.org/jira/browse/OMID-130 > Project: Apache Omid > Issue Type: Bug >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > Fix For: 1.0.1 > > > Some issues to be fixed in 1.0.1 related to > * https://issues.apache.org/jira/browse/PHOENIX-5082 > * https://issues.apache.org/jira/browse/PHOENIX-5090 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-130) Phoenix integration issues
[ https://issues.apache.org/jira/browse/OMID-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-130: -- Fix Version/s: (was: 1.0.1) > Phoenix integration issues > -- > > Key: OMID-130 > URL: https://issues.apache.org/jira/browse/OMID-130 > Project: Apache Omid > Issue Type: Bug >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > > Some issues to be fixed in 1.0.1 related to > * https://issues.apache.org/jira/browse/PHOENIX-5082 > * https://issues.apache.org/jira/browse/PHOENIX-5090 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-130) Phoenix integration issues
[ https://issues.apache.org/jira/browse/OMID-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764411#comment-16764411 ] Ohad Shacham commented on OMID-130: --- OK, cool > Phoenix integration issues > -- > > Key: OMID-130 > URL: https://issues.apache.org/jira/browse/OMID-130 > Project: Apache Omid > Issue Type: Bug >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > > Some issues to be fixed in 1.0.1 related to > * https://issues.apache.org/jira/browse/PHOENIX-5082 > * https://issues.apache.org/jira/browse/PHOENIX-5090 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-130) Omid 1.0.1 release
[ https://issues.apache.org/jira/browse/OMID-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764402#comment-16764402 ] Ohad Shacham edited comment on OMID-130 at 2/10/19 1:02 PM: Hey [~yonigo], You don't need to create an umbrella Jira for a release. In each Jira just change the "Fix version/s" field to 1.0.1. Then we can create a release note for the release and mark its release date. was (Author: ohads): Hey [~yonigo], You don't need to create an umbrella Jira for a release. In each Jira just change the "Fix version/s" field to 1.0.1. > Omid 1.0.1 release > -- > > Key: OMID-130 > URL: https://issues.apache.org/jira/browse/OMID-130 > Project: Apache Omid > Issue Type: Bug >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > > 1.0.1 release to fix bugs and add some enhancements it last release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-130) Omid 1.0.1 release
[ https://issues.apache.org/jira/browse/OMID-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764402#comment-16764402 ] Ohad Shacham commented on OMID-130: --- Hey [~yonigo], You don't need to create an umbrella Jira for a release. In each Jira just change the "Fix version/s" field to 1.0.1. > Omid 1.0.1 release > -- > > Key: OMID-130 > URL: https://issues.apache.org/jira/browse/OMID-130 > Project: Apache Omid > Issue Type: Bug >Reporter: Yonatan Gottesman >Assignee: Yonatan Gottesman >Priority: Major > > 1.0.1 release to fix bugs and add some enhancements it last release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Done On Wed, Jan 16, 2019 at 12:27 PM Ohad Shacham wrote: > > https://issues.apache.org/jira/browse/INFRA-17669 > > > On Tue, Jan 8, 2019 at 9:46 AM Ohad Shacham wrote: > >> >> Guys, >> >> Any obligations that I'll open a ticket at INFRA asking for the >> migration? >> I will open a ticket early next week in case no one answers. >> >> Thanks, >> Ohad >> >> >> -- Forwarded message - >> From: Apache Infrastructure Team >> Date: Thu, Jan 3, 2019 at 3:19 PM >> Subject: [NOTICE] Mandatory migration of git repositories to >> gitbox.apache.org >> To: >> >> >> Hello, omid folks. >> As stated earlier in 2018, all git repositories must be migrated from >> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service >> is being decommissioned. Your project is receiving this email because >> you still have repositories on git-wip-us that needs to be migrated. >> >> The following repositories on git-wip-us belong to your project: >> - incubator-omid.git >> - incubator-omid-site.git >> >> >> We are now entering the mandated (coordinated) move stage of the roadmap, >> and you are asked to please coordinate migration with the Apache >> Infrastructure Team before February 7th. All repositories not migrated >> on February 7th will be mass migrated without warning, and we'd appreciate >> it if we could work together to avoid a big mess that day :-). >> >> Moving to gitbox means you will get full write access on GitHub as well, >> and be able to close/merge pull requests and much more. >> >> To have your repositories moved, please follow these steps: >> >> - Ensure consensus on the move (a link to a lists.apache.org thread will >> suffice for us as evidence). >> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA >> >> Your migration should only take a few minutes. If you wish to migrate >> at a specific time of day or date, please do let us know in the ticket. >> >> As always, we appreciate your understanding and patience as we move >> things around and work to provide better services and features for >> the Apache Family. >> >> Should you wish to contact us with feedback or questions, please do so >> at: us...@infra.apache.org. >> >> >> With regards, >> Apache Infrastructure >> >>
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
https://issues.apache.org/jira/browse/INFRA-17669 On Tue, Jan 8, 2019 at 9:46 AM Ohad Shacham wrote: > > Guys, > > Any obligations that I'll open a ticket at INFRA asking for the migration? > I will open a ticket early next week in case no one answers. > > Thanks, > Ohad > > > -- Forwarded message - > From: Apache Infrastructure Team > Date: Thu, Jan 3, 2019 at 3:19 PM > Subject: [NOTICE] Mandatory migration of git repositories to > gitbox.apache.org > To: > > > Hello, omid folks. > As stated earlier in 2018, all git repositories must be migrated from > the git-wip-us.apache.org URL to gitbox.apache.org, as the old service > is being decommissioned. Your project is receiving this email because > you still have repositories on git-wip-us that needs to be migrated. > > The following repositories on git-wip-us belong to your project: > - incubator-omid.git > - incubator-omid-site.git > > > We are now entering the mandated (coordinated) move stage of the roadmap, > and you are asked to please coordinate migration with the Apache > Infrastructure Team before February 7th. All repositories not migrated > on February 7th will be mass migrated without warning, and we'd appreciate > it if we could work together to avoid a big mess that day :-). > > Moving to gitbox means you will get full write access on GitHub as well, > and be able to close/merge pull requests and much more. > > To have your repositories moved, please follow these steps: > > - Ensure consensus on the move (a link to a lists.apache.org thread will > suffice for us as evidence). > - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA > > Your migration should only take a few minutes. If you wish to migrate > at a specific time of day or date, please do let us know in the ticket. > > As always, we appreciate your understanding and patience as we move > things around and work to provide better services and features for > the Apache Family. > > Should you wish to contact us with feedback or questions, please do so > at: us...@infra.apache.org. > > > With regards, > Apache Infrastructure > >
Fwd: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Guys, Any obligations that I'll open a ticket at INFRA asking for the migration? I will open a ticket early next week in case no one answers. Thanks, Ohad -- Forwarded message - From: Apache Infrastructure Team Date: Thu, Jan 3, 2019 at 3:19 PM Subject: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org To: Hello, omid folks. As stated earlier in 2018, all git repositories must be migrated from the git-wip-us.apache.org URL to gitbox.apache.org, as the old service is being decommissioned. Your project is receiving this email because you still have repositories on git-wip-us that needs to be migrated. The following repositories on git-wip-us belong to your project: - incubator-omid.git - incubator-omid-site.git We are now entering the mandated (coordinated) move stage of the roadmap, and you are asked to please coordinate migration with the Apache Infrastructure Team before February 7th. All repositories not migrated on February 7th will be mass migrated without warning, and we'd appreciate it if we could work together to avoid a big mess that day :-). Moving to gitbox means you will get full write access on GitHub as well, and be able to close/merge pull requests and much more. To have your repositories moved, please follow these steps: - Ensure consensus on the move (a link to a lists.apache.org thread will suffice for us as evidence). - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA Your migration should only take a few minutes. If you wish to migrate at a specific time of day or date, please do let us know in the ticket. As always, we appreciate your understanding and patience as we move things around and work to provide better services and features for the Apache Family. Should you wish to contact us with feedback or questions, please do so at: us...@infra.apache.org. With regards, Apache Infrastructure
[jira] [Commented] (OMID-123) Allow starting Omid on machines without en or eth interfaces.
[
https://issues.apache.org/jira/browse/OMID-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735138#comment-16735138
]
Ohad Shacham commented on OMID-123:
---
[~lhofhansl], ya you are right.
If it won't work then it will throw an exception at the same place.
> Allow starting Omid on machines without en or eth interfaces.
> -
>
> Key: OMID-123
> URL: https://issues.apache.org/jira/browse/OMID-123
> Project: Apache Omid
> Issue Type: Improvement
>Reporter: Lars Hofhansl
>Assignee: Yonatan Gottesman
>Priority: Major
> Attachments: OMID-123.txt
>
>
> Currently there's an assumption that there must be an eth* or a configured
> en* interface in order to bind to a specific address.
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: No network
> 'en*'/'eth*' interfaces found
> at
> org.apache.omid.NetworkUtils.getDefaultNetworkInterface(NetworkUtils.java:52)
> at org.apache.omid.tso.TSOServerConfig.(TSOServerConfig.java:88)
> at org.apache.omid.tso.TSOServerConfig.(TSOServerConfig.java:56)
> at org.apache.omid.tso.TSOServer.main(TSOServer.java:147)
> {code}
> The first question is: Why don't we just allow to bind to ::?
> Second, we can at least provide a default way to start when no en/eth
> interface is available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OMID-123) Allow starting Omid on machines without en or eth interfaces.
[
https://issues.apache.org/jira/browse/OMID-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732786#comment-16732786
]
Ohad Shacham commented on OMID-123:
---
We do need to get the TSO machine ip address since in HA mode this address is
written to the zNode and later on used by the client. We can add a default way
that will use the local host and will work when the TSO is located on the same
machine as the client.
> Allow starting Omid on machines without en or eth interfaces.
> -
>
> Key: OMID-123
> URL: https://issues.apache.org/jira/browse/OMID-123
> Project: Apache Omid
> Issue Type: Improvement
>Reporter: Lars Hofhansl
>Assignee: Yonatan Gottesman
>Priority: Major
> Attachments: OMID-123.txt
>
>
> Currently there's an assumption that there must be an eth* or a configured
> en* interface in order to bind to a specific address.
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: No network
> 'en*'/'eth*' interfaces found
> at
> org.apache.omid.NetworkUtils.getDefaultNetworkInterface(NetworkUtils.java:52)
> at org.apache.omid.tso.TSOServerConfig.(TSOServerConfig.java:88)
> at org.apache.omid.tso.TSOServerConfig.(TSOServerConfig.java:56)
> at org.apache.omid.tso.TSOServer.main(TSOServer.java:147)
> {code}
> The first question is: Why don't we just allow to bind to ::?
> Second, we can at least provide a default way to start when no en/eth
> interface is available.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OMID-124) HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads
[ https://issues.apache.org/jira/browse/OMID-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-124: -- Fix Version/s: 1.0.1 > HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads > -- > > Key: OMID-124 > URL: https://issues.apache.org/jira/browse/OMID-124 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Critical > Fix For: 1.0.1 > > Attachments: OMID-124.txt, omid124.patch > > > I found that as soon as any transaction is written in HBase, the region > server subsequently fails to shut down. > I tracked it down the HBaseClient in HBaseCommitTable. I think this should > generally create daemon threads only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-124) HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads
[ https://issues.apache.org/jira/browse/OMID-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731343#comment-16731343 ] Ohad Shacham commented on OMID-124: --- [~yonigo], OK it is for the test base. LGTM. > HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads > -- > > Key: OMID-124 > URL: https://issues.apache.org/jira/browse/OMID-124 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Critical > Attachments: OMID-124.txt, omid124.patch > > > I found that as soon as any transaction is written in HBase, the region > server subsequently fails to shut down. > I tracked it down the HBaseClient in HBaseCommitTable. I think this should > generally create daemon threads only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OMID-124) HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads
[ https://issues.apache.org/jira/browse/OMID-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731322#comment-16731322 ] Ohad Shacham edited comment on OMID-124 at 12/31/18 1:49 PM: - Are we sure we would like change the default to LOW_CPU? I would benchmark first. If we do then I would create another Jira for that. was (Author: ohads): Are we sure we would like change the default to LOW_CPU? I would benchmark first. > HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads > -- > > Key: OMID-124 > URL: https://issues.apache.org/jira/browse/OMID-124 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Critical > Attachments: OMID-124.txt, omid124.patch > > > I found that as soon as any transaction is written in HBase, the region > server subsequently fails to shut down. > I tracked it down the HBaseClient in HBaseCommitTable. I think this should > generally create daemon threads only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-124) HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads
[ https://issues.apache.org/jira/browse/OMID-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731322#comment-16731322 ] Ohad Shacham commented on OMID-124: --- Are we sure we would like change the default to LOW_CPU? I would benchmark first. > HBaseCommitTable.HBaseClient.deleteBatchExecutor should use daemon threads > -- > > Key: OMID-124 > URL: https://issues.apache.org/jira/browse/OMID-124 > Project: Apache Omid > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: Yonatan Gottesman >Priority: Critical > Attachments: OMID-124.txt, omid124.patch > > > I found that as soon as any transaction is written in HBase, the region > server subsequently fails to shut down. > I tracked it down the HBaseClient in HBaseCommitTable. I think this should > generally create daemon threads only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711069#comment-16711069 ] Ohad Shacham commented on OMID-121: --- Thanks [~alangates] and [~jamestaylor] for signing. > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham resolved OMID-121. --- Resolution: Fixed > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham closed OMID-121. - > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Omid 1.0.0 Released
The Omid team is happy to announce the Omid 1.0.0 release. This release contains features required for the integration with Apache Phoenix, as well as a new low latency algorithm that distributes the commit.
[jira] [Commented] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708291#comment-16708291 ] Ohad Shacham commented on OMID-121: --- Thanks [~alangates], I post in the wiki. Thanks [~fperezsorrosal], I will include in future reports. In any case, in the wiki page only James and Alan are written. I didn't change that. > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Assignee: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham reassigned OMID-121: - Assignee: Ohad Shacham > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham > Assignee: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706713#comment-16706713 ] Ohad Shacham commented on OMID-121: --- Hi [~giacomotaylor] and [~alangates], Could you please review? Thanks, Ohad > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706711#comment-16706711 ] Ohad Shacham commented on OMID-121: --- Omid Omid is a flexible, reliable, high performant and scalable ACID transactional framework that allows client applications to execute transactions on top of MVCC key/value-based NoSQL datastores (currently Apache HBase) providing Snapshot Isolation guarantees on the accessed data. Omid has been incubating since 2016-03-28. Three most important issues to address in the move towards graduation: # Finish integration with Apache Phoenix – Omid side was implemented and released. # Document additional features added for the integration with Apache Phoenix, as well as, the low latency algorithm. # Get positive feedback from other projects currently in Apache. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? # New committer, Yonatan Gottesman, was added to Omid’s community. Yonatan is very active and contributed to the integration with Phoenix. Moreover, Yonattan implemented the low latency version of Omid which is currently part of release 1.0.0. # Integration with Apache Phoenix will be ready in a few days, early December. How has the project developed since the last report? # The vote for major release 1.0.0 passed successfully in the incubator general list. This release includes all the Phoenix required features. The release is currently being deployed to Nexus and a formal announcement of the release will be send shortly. # Omid and Apache Phoenix integration is at its final stage. Omid release 1.0.0 includes all Phoenix required features, therefore, from the Omid side, the integration with Phoenix is over. The Phoenix code is also ready and currently located in a feature branch that will be merged in a few days. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [] Community building [X ] Nearing graduation [ ] Other: Date of last release: 2018-06-10 When were the last committers or PPMC members elected? 2018-9-25 Signed-off-by: [ ](omid) Alan Gates Comments: [ ](omid) Lars Hofhansl Comments: [ ](omid) Flavio P. Junqueira Comments: [ ](omid) Thejas Nair Comments: [ ](omid) James Taylor Comments: > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OMID-121) Apache Incubator report - December 2018
[ https://issues.apache.org/jira/browse/OMID-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ohad Shacham updated OMID-121: -- Description: Provide a report for September 1, 2018 - November 31, 2018 > Apache Incubator report - December 2018 > --- > > Key: OMID-121 > URL: https://issues.apache.org/jira/browse/OMID-121 > Project: Apache Omid > Issue Type: Task > Reporter: Ohad Shacham >Priority: Major > > Provide a report for September 1, 2018 - November 31, 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OMID-121) Apache Incubator report - December 2018
Ohad Shacham created OMID-121: - Summary: Apache Incubator report - December 2018 Key: OMID-121 URL: https://issues.apache.org/jira/browse/OMID-121 Project: Apache Omid Issue Type: Task Reporter: Ohad Shacham -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Incubator Podling Report (Due 5th December)
Hi Justin, I will complete the report tomorrow morning. Thanks, Ohad On Sun, Dec 2, 2018 at 10:28 PM Justin Mclean wrote: > Hi, > > The incubator PMC would appreciated if you could complete the podling > report on time it's due on 5th December in a few days. It takes time to > prepare the incubator report, have your mentors sign off the report and for > the board to review it, so it's best if you can get it in early. > > Thanks, > Justin > >
Please vote for Omid release 1.0.0 in the incubator general list
Guys, Could anyone please vote for Omid release 1.0.0 in the incubator general list? James and Josh already voted and we need one more vote in order to close the release. Thanks! Ohad
